System and Method for Cache Replacement Using Conservative Set Dueling

ABSTRACT

A processor includes a set associative cache and a cache controller. The cache controller makes an initial association between first and second groups of sampled sets in the cache and first and second cache replacement policies. Follower sets in the cache are initially associated with the more conservative of the two policies. Following cache line insertions in a first epoch, the associations between the groups of sampled sets and cache replacement policies are swapped for the next epoch. If the less conservative policy outperforms the more conservative policy during two consecutive epochs, the follower sets are associated with the less conservative policy for the next epoch. Subsequently, if the more conservative policy outperforms the less conservative policy during any epoch, the follower sets are again associated with the more conservative policy. Performance may be measured based the number of cache misses associated with each policy.

FIELD OF THE INVENTION

The present disclosure pertains to the field of processing logic, microprocessors, and associated instruction set architecture that, when executed by the processor or other processing logic, perform logical, mathematical, or other functional operations.

DESCRIPTION OF RELATED ART

Multiprocessor systems are becoming more and more common. In order to take advantage of multiprocessor systems, code to be executed may be separated into multiple threads for execution by various processing entities. Each thread may be executed in parallel with one another. Pipelining of applications may be implemented in systems in order to more efficiently execute applications. Instructions as they are received on a processor may be decoded into terms or instruction words that are native, or more native, for execution on the processor. Each processor may include a cache or multiple caches. Processors may be implemented in a system on chip.

DESCRIPTION OF THE FIGURES

Embodiments are illustrated by way of example and not limitation in the Figures of the accompanying drawings:

FIG. 1A is a block diagram of an exemplary computer system formed with a processor that may include execution units to execute an instruction, in accordance with embodiments of the present disclosure;

FIG. 1B illustrates a data processing system, in accordance with embodiments of the present disclosure;

FIG. 1C illustrates other embodiments of a data processing system for performing text string comparison operations;

FIG. 2 is a block diagram of the micro-architecture for a processor that may include logic circuits to perform instructions, in accordance with embodiments of the present disclosure;

FIG. 3A illustrates various packed data type representations in multimedia registers, in accordance with embodiments of the present disclosure;

FIG. 3B illustrates possible in-register data storage formats, in accordance with embodiments of the present disclosure;

FIG. 3C illustrates various signed and unsigned packed data type representations in multimedia registers, in accordance with embodiments of the present disclosure;

FIG. 3D illustrates an embodiment of an operation encoding format;

FIG. 3E illustrates another possible operation encoding format having forty or more bits, in accordance with embodiments of the present disclosure;

FIG. 3F illustrates yet another possible operation encoding format, in accordance with embodiments of the present disclosure;

FIG. 4A is a block diagram illustrating an in-order pipeline and a register renaming stage, out-of-order issue/execution pipeline, in accordance with embodiments of the present disclosure;

FIG. 4B is a block diagram illustrating an in-order architecture core and a register renaming logic, out-of-order issue/execution logic to be included in a processor, in accordance with embodiments of the present disclosure;

FIG. 5A is a block diagram of a processor, in accordance with embodiments of the present disclosure;

FIG. 5B is a block diagram of an example implementation of a core, in accordance with embodiments of the present disclosure;

FIG. 6 is a block diagram of a system, in accordance with embodiments of the present disclosure;

FIG. 7 is a block diagram of a second system, in accordance with embodiments of the present disclosure;

FIG. 8 is a block diagram of a third system in accordance with embodiments of the present disclosure;

FIG. 9 is a block diagram of a system-on-a-chip, in accordance with embodiments of the present disclosure;

FIG. 10 illustrates a processor containing a central processing unit and a graphics processing unit which may perform at least one instruction, in accordance with embodiments of the present disclosure;

FIG. 11 is a block diagram illustrating the development of IP cores, in accordance with embodiments of the present disclosure;

FIG. 12 illustrates how an instruction of a first type may be emulated by a processor of a different type, in accordance with embodiments of the present disclosure;

FIG. 13 illustrates a block diagram contrasting the use of a software instruction converter to convert binary instructions in a source instruction set to binary instructions in a target instruction set, in accordance with embodiments of the present disclosure;

FIG. 14 is a block diagram of an instruction set architecture of a processor, in accordance with embodiments of the present disclosure;

FIG. 15 is a more detailed block diagram of an instruction set architecture of a processor, in accordance with embodiments of the present disclosure;

FIG. 16 is a block diagram of an execution pipeline for an instruction set architecture of a processor, in accordance with embodiments of the present disclosure;

FIG. 17 is a block diagram of an electronic device for utilizing a processor, in accordance with embodiments of the present disclosure;

FIG. 18 is a block diagram illustrating an example system including a cache controller for conservative set dueling for cache replacement, according to embodiments of the present disclosure;

FIG. 19 is an illustration of an example method for implementing cache replacement using set dueling with set swapping, according to embodiments of the present disclosure;

FIG. 20 is a block diagram illustrating a portion of an example memory subsystem, according to embodiments of the present disclosure;

FIGS. 21A and 21B illustrate the use of set dueling with set swapping for cache replacement, according to embodiments of the present disclosure;

FIG. 22 is an illustration of an example method for implementing cache replacement using conservative set dueling, according to embodiments of the present disclosure; and

FIGS. 23A and 23B further illustrate the use of conservative set dueling for cache replacement, according to embodiments of the present disclosure.

DETAILED DESCRIPTION

The following description describes an instruction and processing logic for implementing cache replacement using conservative set dueling. Such a processing apparatus may include an out-of-order processor. In the following description, numerous specific details such as processing logic, processor types, micro-architectural conditions, events, enablement mechanisms, and the like are set forth in order to provide a more thorough understanding of embodiments of the present disclosure. It will be appreciated, however, by one skilled in the art that the embodiments may be practiced without such specific details. Additionally, some well-known structures, circuits, and the like have not been shown in detail to avoid unnecessarily obscuring embodiments of the present disclosure.

Although the following embodiments are described with reference to a processor, other embodiments are applicable to other types of integrated circuits and logic devices. Similar techniques and teachings of embodiments of the present disclosure may be applied to other types of circuits or semiconductor devices that may benefit from higher pipeline throughput and improved performance. The teachings of embodiments of the present disclosure are applicable to any processor or machine that performs data manipulations. However, the embodiments are not limited to processors or machines that perform 512-bit, 256-bit, 128-bit, 64-bit, 32-bit, or 16-bit data operations and may be applied to any processor and machine in which manipulation or management of data may be performed. In addition, the following description provides examples, and the accompanying drawings show various examples for the purposes of illustration. However, these examples should not be construed in a limiting sense as they are merely intended to provide examples of embodiments of the present disclosure rather than to provide an exhaustive list of all possible implementations of embodiments of the present disclosure.

Although the below examples describe instruction handling and distribution in the context of execution units and logic circuits, other embodiments of the present disclosure may be accomplished by way of a data or instructions stored on a machine-readable, tangible medium, which when performed by a machine cause the machine to perform functions consistent with at least one embodiment of the disclosure. In one embodiment, functions associated with embodiments of the present disclosure are embodied in machine-executable instructions. The instructions may be used to cause a general-purpose or special-purpose processor that may be programmed with the instructions to perform the operations of the present disclosure. Embodiments of the present disclosure may be provided as a computer program product or software which may include a machine or computer-readable medium having stored thereon instructions which may be used to program a computer (or other electronic devices) to perform one or more operations according to embodiments of the present disclosure. Furthermore, operations of embodiments of the present disclosure might be performed by specific hardware components that contain fixed-function logic for performing the operations, or by any combination of programmed computer components and fixed-function hardware components. Throughout this disclosure, unless explicitly stated otherwise, a compound form of a reference numeral refers to the element generically or collectively. Thus, for example, widget 101A or 101-1 refers to an instance of a widget class, which may be referred to collectively as widgets 101 and any one of which may be referred to generically as widget 101.

Instructions used to program logic to perform embodiments of the present disclosure may be stored within a memory in the system, such as DRAM, cache, flash memory, or other storage. Furthermore, the instructions may be distributed via a network or by way of other computer-readable media. Thus a machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), but is not limited to, floppy diskettes, optical disks, Compact Disc, Read-Only Memory (CD-ROMs), and magneto-optical disks, Read-Only Memory (ROMs), Random Access Memory (RAM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), magnetic or optical cards, flash memory, or a tangible, machine-readable storage used in the transmission of information over the Internet via electrical, optical, acoustical or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.). Accordingly, the computer-readable medium may include any type of tangible machine-readable medium suitable for storing or transmitting electronic instructions or information in a form readable by a machine (e.g., a computer).

A design may go through various stages, from creation to simulation to fabrication. Data representing a design may represent the design in a number of manners. First, as may be useful in simulations, the hardware may be represented using a hardware description language or another functional description language. Additionally, a circuit level model with logic and/or transistor gates may be produced at some stages of the design process. Furthermore, designs, at some stage, may reach a level of data representing the physical placement of various devices in the hardware model. In cases wherein some semiconductor fabrication techniques are used, the data representing the hardware model may be the data specifying the presence or absence of various features on different mask layers for masks used to produce the integrated circuit. In any representation of the design, the data may be stored in any form of a machine-readable medium. A memory or a magnetic or optical storage such as a disc may be the machine-readable medium to store information transmitted via optical or electrical wave modulated or otherwise generated to transmit such information. When an electrical carrier wave indicating or carrying the code or design is transmitted, to the extent that copying, buffering, or retransmission of the electrical signal is performed, a new copy may be made. Thus, a communication provider or a network provider may store on a tangible, machine-readable medium, at least temporarily, an article, such as information encoded into a carrier wave, embodying techniques of embodiments of the present disclosure.

In modern processors, a number of different execution units may be used to process and execute a variety of code and instructions. Some instructions may be quicker to complete while others may take a number of clock cycles to complete. The faster the throughput of instructions, the better the overall performance of the processor. Thus it would be advantageous to have as many instructions execute as fast as possible. However, there may be certain instructions that have greater complexity and require more in terms of execution time and processor resources, such as floating point instructions, load/store operations, data moves, etc.

As more computer systems are used in internet, text, and multimedia applications, additional processor support has been introduced over time. In one embodiment, an instruction set may be associated with one or more computer architectures, including data types, instructions, register architecture, addressing modes, memory architecture, interrupt and exception handling, and external input and output (I/O).

In one embodiment, the instruction set architecture (ISA) may be implemented by one or more micro-architectures, which may include processor logic and circuits used to implement one or more instruction sets. Accordingly, processors with different micro-architectures may share at least a portion of a common instruction set. For example, Intel® Pentium 4 processors, Intel® Core™ processors, and processors from Advanced Micro Devices, Inc. of Sunnyvale Calif. implement nearly identical versions of the x86 instruction set (with some extensions that have been added with newer versions), but have different internal designs. Similarly, processors designed by other processor development companies, such as ARM Holdings, Ltd., MIPS, or their licensees or adopters, may share at least a portion of a common instruction set, but may include different processor designs. For example, the same register architecture of the ISA may be implemented in different ways in different micro-architectures using new or well-known techniques, including dedicated physical registers, one or more dynamically allocated physical registers using a register renaming mechanism (e.g., the use of a Register Alias Table (RAT), a Reorder Buffer (ROB) and a retirement register file. In one embodiment, registers may include one or more registers, register architectures, register files, or other register sets that may or may not be addressable by a software programmer.

An instruction may include one or more instruction formats. In one embodiment, an instruction format may indicate various fields (number of bits, location of bits, etc.) to specify, among other things, the operation to be performed and the operands on which that operation will be performed. In a further embodiment, some instruction formats may be further defined by instruction templates (or sub-formats). For example, the instruction templates of a given instruction format may be defined to have different subsets of the instruction format's fields and/or defined to have a given field interpreted differently. In one embodiment, an instruction may be expressed using an instruction format (and, if defined, in a given one of the instruction templates of that instruction format) and specifies or indicates the operation and the operands upon which the operation will operate.

Scientific, financial, auto-vectorized general purpose, RMS (recognition, mining, and synthesis), and visual and multimedia applications (e.g., 2D/3D graphics, image processing, video compression/decompression, voice recognition algorithms and audio manipulation) may require the same operation to be performed on a large number of data items. In one embodiment, Single Instruction Multiple Data (SIMD) refers to a type of instruction that causes a processor to perform an operation on multiple data elements. SIMD technology may be used in processors that may logically divide the bits in a register into a number of fixed-sized or variable-sized data elements, each of which represents a separate value. For example, in one embodiment, the bits in a 64-bit register may be organized as a source operand containing four separate 16-bit data elements, each of which represents a separate 16-bit value. This type of data may be referred to as ‘packed’ data type or ‘vector’ data type, and operands of this data type may be referred to as packed data operands or vector operands. In one embodiment, a packed data item or vector may be a sequence of packed data elements stored within a single register, and a packed data operand or a vector operand may a source or destination operand of a SIMD instruction (or ‘packed data instruction’ or a ‘vector instruction’). In one embodiment, a SIMD instruction specifies a single vector operation to be performed on two source vector operands to generate a destination vector operand (also referred to as a result vector operand) of the same or different size, with the same or different number of data elements, and in the same or different data element order.

SIMD technology, such as that employed by the Intel® CoreTM processors having an instruction set including x86, MMX™, Streaming SIMD Extensions (SSE), SSE2, SSE3, SSE4.1, and SSE4.2 instructions, ARM processors, such as the ARM Cortex® family of processors having an instruction set including the Vector Floating Point (VFP) and/or NEON instructions, and MIPS processors, such as the Loongson family of processors developed by the Institute of Computing Technology (ICT) of the Chinese Academy of Sciences, has enabled a significant improvement in application performance (Core™ and MMX™ are registered trademarks or trademarks of Intel Corporation of Santa Clara, Calif.).

In one embodiment, destination and source registers/data may be generic terms to represent the source and destination of the corresponding data or operation. In some embodiments, they may be implemented by registers, memory, or other storage areas having other names or functions than those depicted. For example, in one embodiment, “DEST1” may be a temporary storage register or other storage area, whereas “SRC1” and “SRC2” may be a first and second source storage register or other storage area, and so forth. In other embodiments, two or more of the SRC and DEST storage areas may correspond to different data storage elements within the same storage area (e.g., a SIMD register). In one embodiment, one of the source registers may also act as a destination register by, for example, writing back the result of an operation performed on the first and second source data to one of the two source registers serving as a destination registers.

FIG. 1A is a block diagram of an exemplary computer system formed with a processor that may include execution units to execute an instruction, in accordance with embodiments of the present disclosure. System 100 may include a component, such as a processor 102 to employ execution units including logic to perform algorithms for process data, in accordance with the present disclosure, such as in the embodiment described herein. System 100 may be representative of processing systems based on the PENTIUM® III, PENTIUM® 4, Xeon™ Itanium®, XScale™ and/or StrongARM™ microprocessors available from Intel Corporation of Santa Clara, Calif., although other systems (including PCs having other microprocessors, engineering workstations, set-top boxes and the like) may also be used. In one embodiment, sample system 100 may execute a version of the WINDOWS™ operating system available from Microsoft Corporation of Redmond, Wash., although other operating systems (UNIX and Linux for example), embedded software, and/or graphical user interfaces, may also be used. Thus, embodiments of the present disclosure are not limited to any specific combination of hardware circuitry and software.

Embodiments are not limited to computer systems. Embodiments of the present disclosure may be used in other devices such as handheld devices and embedded applications. Some examples of handheld devices include cellular phones, Internet Protocol devices, digital cameras, personal digital assistants (PDAs), and handheld PCs. Embedded applications may include a micro controller, a digital signal processor (DSP), system on a chip, network computers (NetPC), set-top boxes, network hubs, wide area network (WAN) switches, or any other system that may perform one or more instructions in accordance with at least one embodiment.

Computer system 100 may include a processor 102 that may include one or more execution units 108 to perform an algorithm to perform at least one instruction in accordance with one embodiment of the present disclosure. One embodiment may be described in the context of a single processor desktop or server system, but other embodiments may be included in a multiprocessor system. System 100 may be an example of a ‘hub’ system architecture. System 100 may include a processor 102 for processing data signals. Processor 102 may include a complex instruction set computer (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, a processor implementing a combination of instruction sets, or any other processor device, such as a digital signal processor, for example. In one embodiment, processor 102 may be coupled to a processor bus 110 that may transmit data signals between processor 102 and other components in system 100. The elements of system 100 may perform conventional functions that are well known to those familiar with the art.

In one embodiment, processor 102 may include a Level 1 (L1) internal cache memory 104. Depending on the architecture, the processor 102 may have a single internal cache or multiple levels of internal cache. In another embodiment, the cache memory may reside external to processor 102. Other embodiments may also include a combination of both internal and external caches depending on the particular implementation and needs. Register file 106 may store different types of data in various registers including integer registers, floating point registers, status registers, and instruction pointer register.

Execution unit 108, including logic to perform integer and floating point operations, also resides in processor 102. Processor 102 may also include a microcode (ucode) ROM that stores microcode for certain macroinstructions. In one embodiment, execution unit 108 may include logic to handle a packed instruction set 109. By including the packed instruction set 109 in the instruction set of a general-purpose processor 102, along with associated circuitry to execute the instructions, the operations used by many multimedia applications may be performed using packed data in a general-purpose processor 102. Thus, many multimedia applications may be accelerated and executed more efficiently by using the full width of a processor's data bus for performing operations on packed data. This may eliminate the need to transfer smaller units of data across the processor's data bus to perform one or more operations one data element at a time.

Embodiments of an execution unit 108 may also be used in micro controllers, embedded processors, graphics devices, DSPs, and other types of logic circuits. System 100 may include a memory 120. Memory 120 may be implemented as a dynamic random access memory (DRAM) device, a static random access memory (SRAM) device, flash memory device, or other memory device. Memory 120 may store instructions 119 and/or data 121 represented by data signals that may be executed by processor 102.

A system logic chip 116 may be coupled to processor bus 110 and memory 120. System logic chip 116 may include a memory controller hub (MCH). Processor 102 may communicate with MCH 116 via a processor bus 110. MCH 116 may provide a high bandwidth memory path 118 to memory 120 for storage of instructions 119 and data 121 and for storage of graphics commands, data and textures. MCH 116 may direct data signals between processor 102, memory 120, and other components in system 100 and to bridge the data signals between processor bus 110, memory 120, and system I/O 122. In some embodiments, the system logic chip 116 may provide a graphics port for coupling to a graphics controller 112. MCH 116 may be coupled to memory 120 through a memory interface 118. Graphics card 112 may be coupled to MCH 116 through an Accelerated Graphics Port (AGP) interconnect 114.

System 100 may use a proprietary hub interface bus 122 to couple MCH 116 to I/O controller hub (ICH) 130. In one embodiment, ICH 130 may provide direct connections to some I/O devices via a local I/O bus. The local I/O bus may include a high-speed I/O bus for connecting peripherals to memory 120, chipset, and processor 102. Examples may include the audio controller 129, firmware hub (flash BIOS) 128, wireless transceiver 126, data storage 124, legacy I/O controller 123 containing user input interface 125 (which may include a keyboard interface), a serial expansion port 127 such as Universal Serial Bus (USB), and a network controller 134. Data storage device 124 may comprise a hard disk drive, a floppy disk drive, a CD-ROM device, a flash memory device, or other mass storage device.

For another embodiment of a system, an instruction in accordance with one embodiment may be used with a system on a chip. One embodiment of a system on a chip comprises of a processor and a memory. The memory for one such system may include a flash memory. The flash memory may be located on the same die as the processor and other system components. Additionally, other logic blocks such as a memory controller or graphics controller may also be located on a system on a chip.

FIG. 1B illustrates a data processing system 140 which implements the principles of embodiments of the present disclosure. It will be readily appreciated by one of skill in the art that the embodiments described herein may operate with alternative processing systems without departure from the scope of embodiments of the disclosure.

Computer system 140 comprises a processing core 159 for performing at least one instruction in accordance with one embodiment. In one embodiment, processing core 159 represents a processing unit of any type of architecture, including but not limited to a CISC, a RISC or a VLIW type architecture. Processing core 159 may also be suitable for manufacture in one or more process technologies and by being represented on a machine-readable media in sufficient detail, may be suitable to facilitate said manufacture.

Processing core 159 comprises an execution unit 142, a set of register files 145, and a decoder 144. Processing core 159 may also include additional circuitry (not shown) which may be unnecessary to the understanding of embodiments of the present disclosure. Execution unit 142 may execute instructions received by processing core 159. In addition to performing typical processor instructions, execution unit 142 may perform instructions in packed instruction set 143 for performing operations on packed data formats. Packed instruction set 143 may include instructions for performing embodiments of the disclosure and other packed instructions. Execution unit 142 may be coupled to register file 145 by an internal bus. Register file 145 may represent a storage area on processing core 159 for storing information, including data. As previously mentioned, it is understood that the storage area may store the packed data might not be critical. Execution unit 142 may be coupled to decoder 144. Decoder 144 may decode instructions received by processing core 159 into control signals and/or microcode entry points. In response to these control signals and/or microcode entry points, execution unit 142 performs the appropriate operations. In one embodiment, the decoder may interpret the opcode of the instruction, which will indicate what operation should be performed on the corresponding data indicated within the instruction.

Processing core 159 may be coupled with bus 141 for communicating with various other system devices, which may include but are not limited to, for example, synchronous dynamic random access memory (SDRAM) control 146, static random access memory (SRAM) control 147, burst flash memory interface 148, personal computer memory card international association (PCMCIA)/compact flash (CF) card control 149, liquid crystal display (LCD) control 150, direct memory access (DMA) controller 151, and alternative bus master interface 152. In one embodiment, data processing system 140 may also comprise an I/O bridge 154 for communicating with various I/O devices via an I/O bus 153. Such I/O devices may include but are not limited to, for example, universal asynchronous receiver/transmitter (UART) 155, universal serial bus (USB) 156, Bluetooth wireless UART 157 and I/O expansion interface 158.

One embodiment of data processing system 140 provides for mobile, network and/or wireless communications and a processing core 159 that may perform SIMD operations including a text string comparison operation. Processing core 159 may be programmed with various audio, video, imaging and communications algorithms including discrete transformations such as a Walsh-Hadamard transform, a fast Fourier transform (FFT), a discrete cosine transform (DCT), and their respective inverse transforms; compression/decompression techniques such as color space transformation, video encode motion estimation or video decode motion compensation; and modulation/demodulation (MODEM) functions such as pulse coded modulation (PCM).

FIG. 1C illustrates other embodiments of a data processing system that performs SIMD text string comparison operations. In one embodiment, data processing system 160 may include a main processor 166, a SIMD coprocessor 161, a cache memory 167, and an input/output system 168. Input/output system 168 may optionally be coupled to a wireless interface 169. SIMD coprocessor 161 may perform operations including instructions in accordance with one embodiment. In one embodiment, processing core 170 may be suitable for manufacture in one or more process technologies and by being represented on a machine-readable media in sufficient detail, may be suitable to facilitate the manufacture of all or part of data processing system 160 including processing core 170.

In one embodiment, SIMD coprocessor 161 comprises an execution unit 162 and a set of register files 164. One embodiment of main processor 166 comprises a decoder 165 to recognize instructions of instruction set 163 including instructions in accordance with one embodiment for execution by execution unit 162. In other embodiments, SIMD coprocessor 161 also comprises at least part of decoder 165 (shown as 165B) to decode instructions of instruction set 163. Processing core 170 may also include additional circuitry (not shown) which may be unnecessary to the understanding of embodiments of the present disclosure.

In operation, main processor 166 executes a stream of data processing instructions that control data processing operations of a general type including interactions with cache memory 167, and input/output system 168. Embedded within the stream of data processing instructions may be SIMD coprocessor instructions. Decoder 165 of main processor 166 recognizes these SIMD coprocessor instructions as being of a type that should be executed by an attached SIMD coprocessor 161. Accordingly, main processor 166 issues these SIMD coprocessor instructions (or control signals representing SIMD coprocessor instructions) on the coprocessor bus 171. From coprocessor bus 171, these instructions may be received by any attached SIMD coprocessors. In this case, SIMD coprocessor 161 may accept and execute any received SIMD coprocessor instructions intended for it.

Data may be received via wireless interface 169 for processing by the SIMD coprocessor instructions. For one example, voice communication may be received in the form of a digital signal, which may be processed by the SIMD coprocessor instructions to regenerate digital audio samples representative of the voice communications. For another example, compressed audio and/or video may be received in the form of a digital bit stream, which may be processed by the SIMD coprocessor instructions to regenerate digital audio samples and/or motion video frames. In one embodiment of processing core 170, main processor 166, and a SIMD coprocessor 161 may be integrated into a single processing core 170 comprising an execution unit 162, a set of register files 164, and a decoder 165 to recognize instructions of instruction set 163 including instructions in accordance with one embodiment.

FIG. 2 is a block diagram of the micro-architecture for a processor 200 that may include logic circuits to perform instructions, in accordance with embodiments of the present disclosure. In some embodiments, an instruction in accordance with one embodiment may be implemented to operate on data elements having sizes of byte, word, doubleword, quadword, etc., as well as datatypes, such as single and double precision integer and floating point datatypes. In one embodiment, in-order front end 201 may implement a part of processor 200 that may fetch instructions to be executed and prepares the instructions to be used later in the processor pipeline. Front end 201 may include several units. In one embodiment, instruction prefetcher 226 fetches instructions from memory and feeds the instructions to an instruction decoder 228 which in turn decodes or interprets the instructions. For example, in one embodiment, the decoder decodes a received instruction into one or more operations called “micro-instructions” or “micro-operations” (also called micro op or uops) that the machine may execute. In other embodiments, the decoder parses the instruction into an opcode and corresponding data and control fields that may be used by the micro-architecture to perform operations in accordance with one embodiment. In one embodiment, trace cache 230 may assemble decoded uops into program ordered sequences or traces in uop queue 234 for execution. When trace cache 230 encounters a complex instruction, microcode ROM 232 provides the uops needed to complete the operation.

Some instructions may be converted into a single micro-op, whereas others need several micro-ops to complete the full operation. In one embodiment, if more than four micro-ops are needed to complete an instruction, decoder 228 may access microcode ROM 232 to perform the instruction. In one embodiment, an instruction may be decoded into a small number of micro ops for processing at instruction decoder 228. In another embodiment, an instruction may be stored within microcode ROM 232 should a number of micro-ops be needed to accomplish the operation. Trace cache 230 refers to an entry point programmable logic array (PLA) to determine a correct micro-instruction pointer for reading the micro-code sequences to complete one or more instructions in accordance with one embodiment from micro-code ROM 232. After microcode ROM 232 finishes sequencing micro-ops for an instruction, front end 201 of the machine may resume fetching micro-ops from trace cache 230.

Out-of-order execution engine 203 may prepare instructions for execution. The out-of-order execution logic has a number of buffers to smooth out and re-order the flow of instructions to optimize performance as they go down the pipeline and get scheduled for execution. The allocator logic in allocator/register renamer 215 allocates the machine buffers and resources that each uop needs in order to execute. The register renaming logic in allocator/register renamer 215 renames logic registers onto entries in a register file. The allocator 215 also allocates an entry for each uop in one of the two uop queues, one for memory operations (memory uop queue 207) and one for non-memory operations (integer/floating point uop queue 205), in front of the instruction schedulers: memory scheduler 209, fast scheduler 202, slow/general floating point scheduler 204, and simple floating point scheduler 206. Uop schedulers 202, 204, 206, determine when a uop is ready to execute based on the readiness of their dependent input register operand sources and the availability of the execution resources the uops need to complete their operation. Fast scheduler 202 of one embodiment may schedule on each half of the main clock cycle while the other schedulers may only schedule once per main processor clock cycle. The schedulers arbitrate for the dispatch ports to schedule uops for execution.

Register files 208, 210 may be arranged between schedulers 202, 204, 206, and execution units 212, 214, 216, 218, 220, 222, 224 in execution block 211. Each of register files 208, 210 perform integer and floating point operations, respectively. Each register file 208, 210, may include a bypass network that may bypass or forward just completed results that have not yet been written into the register file to new dependent uops. Integer register file 208 and floating point register file 210 may communicate data with the other. In one embodiment, integer register file 208 may be split into two separate register files, one register file for low-order thirty-two bits of data and a second register file for high order thirty-two bits of data. Floating point register file 210 may include 128-bit wide entries because floating point instructions typically have operands from 64 to 128 bits in width.

Execution block 211 may contain execution units 212, 214, 216, 218, 220, 222, 224. Execution units 212, 214, 216, 218, 220, 222, 224 may execute the instructions. Execution block 211 may include register files 208, 210 that store the integer and floating point data operand values that the micro-instructions need to execute. In one embodiment, processor 200 may comprise a number of execution units: address generation unit (AGU) 212, AGU 214, fast ALU 216, fast ALU 218, slow ALU 220, floating point ALU 222, floating point move unit 224. In another embodiment, floating point execution blocks 222, 224, may execute floating point, MMX, SIMD, and SSE, or other operations. In yet another embodiment, floating point ALU 222 may include a 64-bit by 64-bit floating point divider to execute divide, square root, and remainder micro-ops. In various embodiments, instructions involving a floating point value may be handled with the floating point hardware. In one embodiment, ALU operations may be passed to high-speed ALU execution units 216, 218. High-speed ALUs 216, 218 may execute fast operations with an effective latency of half a clock cycle. In one embodiment, most complex integer operations go to slow ALU 220 as slow ALU 220 may include integer execution hardware for long-latency type of operations, such as a multiplier, shifts, flag logic, and branch processing. Memory load/store operations may be executed by AGUs 212, 214. In one embodiment, integer ALUs 216, 218, 220 may perform integer operations on 64-bit data operands. In other embodiments, ALUs 216, 218, 220 may be implemented to support a variety of data bit sizes including sixteen, thirty-two, 128, 256, etc. Similarly, floating point units 222, 224 may be implemented to support a range of operands having bits of various widths. In one embodiment, floating point units 222, 224, may operate on 128-bit wide packed data operands in conjunction with SIMD and multimedia instructions.

In one embodiment, uops schedulers 202, 204, 206, dispatch dependent operations before the parent load has finished executing. As uops may be speculatively scheduled and executed in processor 200, processor 200 may also include logic to handle memory misses. If a data load misses in the data cache, there may be dependent operations in flight in the pipeline that have left the scheduler with temporarily incorrect data. A replay mechanism tracks and re-executes instructions that use incorrect data. Only the dependent operations might need to be replayed and the independent ones may be allowed to complete. The schedulers and replay mechanism of one embodiment of a processor may also be designed to catch instruction sequences for text string comparison operations.

The term “registers” may refer to the on-board processor storage locations that may be used as part of instructions to identify operands. In other words, registers may be those that may be usable from the outside of the processor (from a programmer's perspective). However, in some embodiments registers might not be limited to a particular type of circuit. Rather, a register may store data, provide data, and perform the functions described herein. The registers described herein may be implemented by circuitry within a processor using any number of different techniques, such as dedicated physical registers, dynamically allocated physical registers using register renaming, combinations of dedicated and dynamically allocated physical registers, etc. In one embodiment, integer registers store 32-bit integer data. A register file of one embodiment also contains eight multimedia SIMD registers for packed data. For the discussions below, the registers may be understood to be data registers designed to hold packed data, such as 64-bit wide MMX™ registers (also referred to as ‘mm’ registers in some instances) in microprocessors enabled with MMX technology from Intel Corporation of Santa Clara, Calif. These MMX registers, available in both integer and floating point forms, may operate with packed data elements that accompany SIMD and SSE instructions. Similarly, 128-bit wide XMM registers relating to SSE2, SSE3, SSE4, or beyond (referred to generically as “SSEx”) technology may hold such packed data operands. In one embodiment, in storing packed data and integer data, the registers do not need to differentiate between the two data types. In one embodiment, integer and floating point data may be contained in the same register file or different register files. Furthermore, in one embodiment, floating point and integer data may be stored in different registers or the same registers.

In the examples of the following figures, a number of data operands may be described. FIG. 3A illustrates various packed data type representations in multimedia registers, in accordance with embodiments of the present disclosure. FIG. 3A illustrates data types for a packed byte 310, a packed word 320, and a packed doubleword (dword) 330 for 128-bit wide operands. Packed byte format 310 of this example may be 128 bits long and contains sixteen packed byte data elements. A byte may be defined, for example, as eight bits of data. Information for each byte data element may be stored in bit 7 through bit 0 for byte 0, bit 15 through bit 8 for byte 1, bit 23 through bit 16 for byte 2, and finally bit 120 through bit 127 for byte 15. Thus, all available bits may be used in the register. This storage arrangement increases the storage efficiency of the processor. As well, with sixteen data elements accessed, one operation may now be performed on sixteen data elements in parallel.

Generally, a data element may include an individual piece of data that is stored in a single register or memory location with other data elements of the same length. In packed data sequences relating to SSEx technology, the number of data elements stored in a XMM register may be 128 bits divided by the length in bits of an individual data element. Similarly, in packed data sequences relating to MMX and SSE technology, the number of data elements stored in an MMX register may be 64 bits divided by the length in bits of an individual data element. Although the data types illustrated in FIG. 3A may be 128 bits long, embodiments of the present disclosure may also operate with 64-bit wide or other sized operands. Packed word format 320 of this example may be 128 bits long and contains eight packed word data elements. Each packed word contains sixteen bits of information. Packed doubleword format 330 of FIG. 3A may be 128 bits long and contains four packed doubleword data elements. Each packed doubleword data element contains thirty-two bits of information. A packed quadword may be 128 bits long and contain two packed quad-word data elements.

FIG. 3B illustrates possible in-register data storage formats, in accordance with embodiments of the present disclosure. Each packed data may include more than one independent data element. Three packed data formats are illustrated; packed half 341, packed single 342, and packed double 343. One embodiment of packed half 341, packed single 342, and packed double 343 contain fixed-point data elements. For another embodiment one or more of packed half 341, packed single 342, and packed double 343 may contain floating-point data elements. One embodiment of packed half 341 may be 128 bits long containing eight 16-bit data elements. One embodiment of packed single 342 may be 128 bits long and contains four 32-bit data elements. One embodiment of packed double 343 may be 128 bits long and contains two 64-bit data elements. It will be appreciated that such packed data formats may be further extended to other register lengths, for example, to 96-bits, 160-bits, 192-bits, 224-bits, 256-bits or more.

FIG. 3C illustrates various signed and unsigned packed data type representations in multimedia registers, in accordance with embodiments of the present disclosure. Unsigned packed byte representation 344 illustrates the storage of an unsigned packed byte in a SIMD register. Information for each byte data element may be stored in bit 7 through bit 0 for byte 0, bit 15 through bit 8 for byte 1, bit 23 through bit 16 for byte 2, and finally bit 120 through bit 127 for byte 15. Thus, all available bits may be used in the register. This storage arrangement may increase the storage efficiency of the processor. As well, with sixteen data elements accessed, one operation may now be performed on sixteen data elements in a parallel fashion. Signed packed byte representation 345 illustrates the storage of a signed packed byte. Note that the eighth bit of every byte data element may be the sign indicator. Unsigned packed word representation 346 illustrates how word seven through word zero may be stored in a SIMD register. Signed packed word representation 347 may be similar to the unsigned packed word in-register representation 346. Note that the sixteenth bit of each word data element may be the sign indicator. Unsigned packed doubleword representation 348 shows how doubleword data elements are stored. Signed packed doubleword representation 349 may be similar to unsigned packed doubleword in-register representation 348. Note that the necessary sign bit may be the thirty-second bit of each doubleword data element.

FIG. 3D illustrates an embodiment of an operation encoding (opcode). Furthermore, format 360 may include register/memory operand addressing modes corresponding with a type of opcode format described in the “IA-32 Intel Architecture Software Developer's Manual Volume 2: Instruction Set Reference,” which is available from Intel Corporation, Santa Clara, Calif. on the world-wide-web (www) at intel.com/design/litcentr. In one embodiment, an instruction may be encoded by one or more of fields 361 and 362. Up to two operand locations per instruction may be identified, including up to two source operand identifiers 364 and 365. In one embodiment, destination operand identifier 366 may be the same as source operand identifier 364, whereas in other embodiments they may be different. In another embodiment, destination operand identifier 366 may be the same as source operand identifier 365, whereas in other embodiments they may be different. In one embodiment, one of the source operands identified by source operand identifiers 364 and 365 may be overwritten by the results of the text string comparison operations, whereas in other embodiments identifier 364 corresponds to a source register element and identifier 365 corresponds to a destination register element. In one embodiment, operand identifiers 364 and 365 may identify 32-bit or 64-bit source and destination operands.

FIG. 3E illustrates another possible operation encoding (opcode) format 370, having forty or more bits, in accordance with embodiments of the present disclosure. Opcode format 370 corresponds with opcode format 360 and comprises an optional prefix byte 378. An instruction according to one embodiment may be encoded by one or more of fields 378, 371, and 372. Up to two operand locations per instruction may be identified by source operand identifiers 374 and 375 and by prefix byte 378. In one embodiment, prefix byte 378 may be used to identify 32-bit or 64-bit source and destination operands. In one embodiment, destination operand identifier 376 may be the same as source operand identifier 374, whereas in other embodiments they may be different. For another embodiment, destination operand identifier 376 may be the same as source operand identifier 375, whereas in other embodiments they may be different. In one embodiment, an instruction operates on one or more of the operands identified by operand identifiers 374 and 375 and one or more operands identified by operand identifiers 374 and 375 may be overwritten by the results of the instruction, whereas in other embodiments, operands identified by identifiers 374 and 375 may be written to another data element in another register. Opcode formats 360 and 370 allow register to register, memory to register, register by memory, register by register, register by immediate, register to memory addressing specified in part by MOD fields 363 and 373 and by optional scale-index-base and displacement bytes.

FIG. 3F illustrates yet another possible operation encoding (opcode) format, in accordance with embodiments of the present disclosure. 64-bit single instruction multiple data (SIMD) arithmetic operations may be performed through a coprocessor data processing (CDP) instruction. Operation encoding (opcode) format 380 depicts one such CDP instruction having CDP opcode fields 382 and 389. The type of CDP instruction, for another embodiment, operations may be encoded by one or more of fields 383, 384, 387, and 388. Up to three operand locations per instruction may be identified, including up to two source operand identifiers 385 and 390 and one destination operand identifier 386. One embodiment of the coprocessor may operate on eight, sixteen, thirty-two, and 64-bit values. In one embodiment, an instruction may be performed on integer data elements. In some embodiments, an instruction may be executed conditionally, using condition field 381. For some embodiments, source data sizes may be encoded by field 383. In some embodiments, Zero (Z), negative (N), carry (C), and overflow (V) detection may be done on SIMD fields. For some instructions, the type of saturation may be encoded by field 384.

FIG. 4A is a block diagram illustrating an in-order pipeline and a register renaming stage, out-of-order issue/execution pipeline, in accordance with embodiments of the present disclosure. FIG. 4B is a block diagram illustrating an in-order architecture core and a register renaming logic, out-of-order issue/execution logic to be included in a processor, in accordance with embodiments of the present disclosure. The solid lined boxes in FIG. 4A illustrate the in-order pipeline, while the dashed lined boxes illustrates the register renaming, out-of-order issue/execution pipeline. Similarly, the solid lined boxes in FIG. 4B illustrate the in-order architecture logic, while the dashed lined boxes illustrates the register renaming logic and out-of-order issue/execution logic.

In FIG. 4A, a processor pipeline 400 may include a fetch stage 402, a length decode stage 404, a decode stage 406, an allocation stage 408, a renaming stage 410, a scheduling (also known as a dispatch or issue) stage 412, a register read/memory read stage 414, an execute stage 416, a write-back/memory-write stage 418, an exception handling stage 422, and a commit stage 424.

In FIG. 4B, arrows denote a coupling between two or more units and the direction of the arrow indicates a direction of data flow between those units. FIG. 4B shows processor core 490 including a front end unit 430 coupled to an execution engine unit 450, and both may be coupled to a memory unit 470.

Core 490 may be a reduced instruction set computing (RISC) core, a complex instruction set computing (CISC) core, a very long instruction word (VLIW) core, or a hybrid or alternative core type. In one embodiment, core 490 may be a special-purpose core, such as, for example, a network or communication core, compression engine, graphics core, or the like.

Front end unit 430 may include a branch prediction unit 432 coupled to an instruction cache unit 434. Instruction cache unit 434 may be coupled to an instruction translation lookaside buffer (TLB) 436. TLB 436 may be coupled to an instruction fetch unit 438, which is coupled to a decode unit 440. Decode unit 440 may decode instructions, and generate as an output one or more micro-operations, micro-code entry points, microinstructions, other instructions, or other control signals, which may be decoded from, or which otherwise reflect, or may be derived from, the original instructions. The decoder may be implemented using various different mechanisms. Examples of suitable mechanisms include, but are not limited to, look-up tables, hardware implementations, programmable logic arrays (PLAs), microcode read-only memories (ROMs), etc. In one embodiment, instruction cache unit 434 may be further coupled to a level 2 (L2) cache unit 476 in memory unit 470. Decode unit 440 may be coupled to a rename/allocator unit 452 in execution engine unit 450.

Execution engine unit 450 may include rename/allocator unit 452 coupled to a retirement unit 454 and a set of one or more scheduler units 456. Scheduler units 456 represent any number of different schedulers, including reservations stations, central instruction window, etc. Scheduler units 456 may be coupled to physical register file units 458. Each of physical register file units 458 represents one or more physical register files, different ones of which store one or more different data types, such as scalar integer, scalar floating point, packed integer, packed floating point, vector integer, vector floating point, etc., status (e.g., an instruction pointer that is the address of the next instruction to be executed), etc. Physical register file units 458 may be overlapped by retirement unit 454 to illustrate various ways in which register renaming and out-of-order execution may be implemented (e.g., using one or more reorder buffers and one or more retirement register files, using one or more future files, one or more history buffers, and one or more retirement register files; using register maps and a pool of registers; etc.). Generally, the architectural registers may be visible from the outside of the processor or from a programmer's perspective. The registers might not be limited to any known particular type of circuit. Various different types of registers may be suitable as long as they store and provide data as described herein. Examples of suitable registers include, but might not be limited to, dedicated physical registers, dynamically allocated physical registers using register renaming, combinations of dedicated and dynamically allocated physical registers, etc. Retirement unit 454 and physical register file units 458 may be coupled to execution clusters 460. Execution clusters 460 may include a set of one or more execution units 462 and a set of one or more memory access units 464. Execution units 462 may perform various operations (e.g., shifts, addition, subtraction, multiplication) and on various types of data (e.g., scalar floating point, packed integer, packed floating point, vector integer, vector floating point). While some embodiments may include a number of execution units dedicated to specific functions or sets of functions, other embodiments may include only one execution unit or multiple execution units that all perform all functions. Scheduler units 456, physical register file units 458, and execution clusters 460 are shown as being possibly plural because certain embodiments create separate pipelines for certain types of data/operations (e.g., a scalar integer pipeline, a scalar floating point/packed integer/packed floating point/vector integer/vector floating point pipeline, and/or a memory access pipeline that each have their own scheduler unit, physical register file unit, and/or execution cluster—and in the case of a separate memory access pipeline, certain embodiments may be implemented in which only the execution cluster of this pipeline has memory access units 464). It should also be understood that where separate pipelines are used, one or more of these pipelines may be out-of-order issue/execution and the rest in-order.

The set of memory access units 464 may be coupled to memory unit 470, which may include a data TLB unit 472 coupled to a data cache unit 474 coupled to a level 2 (L2) cache unit 476. In one exemplary embodiment, memory access units 464 may include a load unit, a store address unit, and a store data unit, each of which may be coupled to data TLB unit 472 in memory unit 470. L2 cache unit 476 may be coupled to one or more other levels of cache and eventually to a main memory. While FIG. 4B illustrates an embodiment in which instruction cache unit 434, data cache unit 474, and level 2 (L2) cache unit 476 reside within core 490, in other embodiments one or more caches or cache units may be internal to a core, external to a core, or apportioned internal to and external to a core in different combinations.

By way of example, the exemplary register renaming, out-of-order issue/execution core architecture may implement pipeline 400 as follows: 1) instruction fetch 438 may perform fetch and length decoding stages 402 and 404; 2) decode unit 440 may perform decode stage 406; 3) rename/allocator unit 452 may perform allocation stage 408 and renaming stage 410; 4) scheduler units 456 may perform schedule stage 412; 5) physical register file units 458 and memory unit 470 may perform register read/memory read stage 414; execution cluster 460 may perform execute stage 416; 6) memory unit 470 and physical register file units 458 may perform write-back/memory-write stage 418; 7) various units may be involved in the performance of exception handling stage 422; and 8) retirement unit 454 and physical register file units 458 may perform commit stage 424.

Core 490 may support one or more instructions sets (e.g., the x86 instruction set (with some extensions that have been added with newer versions); the MIPS instruction set of MIPS Technologies of Sunnyvale, Calif.; the ARM instruction set (with optional additional extensions such as NEON) of ARM Holdings of Sunnyvale, Calif.).

It should be understood that the core may support multithreading (executing two or more parallel sets of operations or threads) in a variety of manners. Multithreading support may be performed by, for example, including time sliced multithreading, simultaneous multithreading (where a single physical core provides a logical core for each of the threads that physical core is simultaneously multithreading), or a combination thereof. Such a combination may include, for example, time sliced fetching and decoding and simultaneous multithreading thereafter such as in the Intel® Hyperthreading technology.

While register renaming may be described in the context of out-of-order execution, it should be understood that register renaming may be used in an in-order architecture. While the illustrated embodiment of the processor may also include a separate instruction and data cache units 434/474 and a shared L2 cache unit 476, other embodiments may have a single internal cache for both instructions and data, such as, for example, a Level 1 (L1) internal cache, or multiple levels of internal cache. In some embodiments, the system may include a combination of an internal cache and an external cache that may be external to the core and/or the processor. In other embodiments, all of the caches may be external to the core and/or the processor.

FIG. 5A is a block diagram of a processor 500, in accordance with embodiments of the present disclosure. In one embodiment, processor 500 may include a multicore processor. Processor 500 may include a system agent 510 communicatively coupled to one or more cores 502. Furthermore, cores 502 and system agent 510 may be communicatively coupled to one or more caches 506. Cores 502, system agent 510, and caches 506 may be communicatively coupled via one or more memory control units 552. Furthermore, cores 502, system agent 510, and caches 506 may be communicatively coupled to a graphics module 560 via memory control units 552.

Processor 500 may include any suitable mechanism for interconnecting cores 502, system agent 510, and caches 506, and graphics module 560. In one embodiment, processor 500 may include a ring-based interconnect unit 508 to interconnect cores 502, system agent 510, and caches 506, and graphics module 560. In other embodiments, processor 500 may include any number of well-known techniques for interconnecting such units. Ring-based interconnect unit 508 may utilize memory control units 552 to facilitate interconnections.

Processor 500 may include a memory hierarchy comprising one or more levels of caches within the cores, one or more shared cache units such as caches 506, or external memory (not shown) coupled to the set of integrated memory controller units 552. Caches 506 may include any suitable cache. In one embodiment, caches 506 may include one or more mid-level caches, such as level 2 (L2), level 3 (L3), level 4 (L4), or other levels of cache, a last level cache (LLC), and/or combinations thereof.

In various embodiments, one or more of cores 502 may perform multi-threading. System agent 510 may include components for coordinating and operating cores 502. System agent unit 510 may include for example a power control unit (PCU). The PCU may be or include logic and components needed for regulating the power state of cores 502. System agent 510 may include a display engine 512 for driving one or more externally connected displays or graphics module 560. System agent 510 may include an interface 514 for communications busses for graphics. In one embodiment, interface 514 may be implemented by PCI Express (PCIe). In a further embodiment, interface 514 may be implemented by PCI Express Graphics (PEG). System agent 510 may include a direct media interface (DMI) 516. DMI 516 may provide links between different bridges on a motherboard or other portion of a computer system. System agent 510 may include a PCIe bridge 518 for providing PCIe links to other elements of a computing system. PCIe bridge 518 may be implemented using a memory controller 520 and coherence logic 522.

Cores 502 may be implemented in any suitable manner. Cores 502 may be homogenous or heterogeneous in terms of architecture and/or instruction set. In one embodiment, some of cores 502 may be in-order while others may be out-of-order. In another embodiment, two or more of cores 502 may execute the same instruction set, while others may execute only a subset of that instruction set or a different instruction set.

Processor 500 may include a general-purpose processor, such as a Core™ i3, i5, i7, 2 Duo and Quad, Xeon™, Itanium™, XScale™ or StrongARM™ processor, which may be available from Intel Corporation, of Santa Clara, Calif. Processor 500 may be provided from another company, such as ARM Holdings, Ltd, MIPS, etc. Processor 500 may be a special-purpose processor, such as, for example, a network or communication processor, compression engine, graphics processor, co-processor, embedded processor, or the like. Processor 500 may be implemented on one or more chips. Processor 500 may be a part of and/or may be implemented on one or more substrates using any of a number of process technologies, such as, for example, BiCMOS, CMOS, or NMOS.

In one embodiment, a given one of caches 506 may be shared by multiple ones of cores 502. In another embodiment, a given one of caches 506 may be dedicated to one of cores 502. The assignment of caches 506 to cores 502 may be handled by a cache controller or other suitable mechanism. A given one of caches 506 may be shared by two or more cores 502 by implementing time-slices of a given cache 506.

Graphics module 560 may implement an integrated graphics processing subsystem. In one embodiment, graphics module 560 may include a graphics processor. Furthermore, graphics module 560 may include a media engine 565. Media engine 565 may provide media encoding and video decoding.

FIG. 5B is a block diagram of an example implementation of a core 502, in accordance with embodiments of the present disclosure. Core 502 may include a front end 570 communicatively coupled to an out-of-order engine 580. Core 502 may be communicatively coupled to other portions of processor 500 through cache hierarchy 503.

Front end 570 may be implemented in any suitable manner, such as fully or in part by front end 201 as described above. In one embodiment, front end 570 may communicate with other portions of processor 500 through cache hierarchy 503. In a further embodiment, front end 570 may fetch instructions from portions of processor 500 and prepare the instructions to be used later in the processor pipeline as they are passed to out-of-order execution engine 580.

Out-of-order execution engine 580 may be implemented in any suitable manner, such as fully or in part by out-of-order execution engine 203 as described above. Out-of-order execution engine 580 may prepare instructions received from front end 570 for execution. Out-of-order execution engine 580 may include an allocate module 582. In one embodiment, allocate module 582 may allocate resources of processor 500 or other resources, such as registers or buffers, to execute a given instruction. Allocate module 582 may make allocations in schedulers, such as a memory scheduler, fast scheduler, or floating point scheduler. Such schedulers may be represented in FIG. 5B by resource schedulers 584. Allocate module 582 may be implemented fully or in part by the allocation logic described in conjunction with FIG. 2. Resource schedulers 584 may determine when an instruction is ready to execute based on the readiness of a given resource's sources and the availability of execution resources needed to execute an instruction. Resource schedulers 584 may be implemented by, for example, schedulers 202, 204, 206 as discussed above. Resource schedulers 584 may schedule the execution of instructions upon one or more resources. In one embodiment, such resources may be internal to core 502, and may be illustrated, for example, as resources 586. In another embodiment, such resources may be external to core 502 and may be accessible by, for example, cache hierarchy 503. Resources may include, for example, memory, caches, register files, or registers. Resources internal to core 502 may be represented by resources 586 in FIG. 5B. As necessary, values written to or read from resources 586 may be coordinated with other portions of processor 500 through, for example, cache hierarchy 503. As instructions are assigned resources, they may be placed into a reorder buffer 588. Reorder buffer 588 may track instructions as they are executed and may selectively reorder their execution based upon any suitable criteria of processor 500. In one embodiment, reorder buffer 588 may identify instructions or a series of instructions that may be executed independently. Such instructions or a series of instructions may be executed in parallel from other such instructions. Parallel execution in core 502 may be performed by any suitable number of separate execution blocks or virtual processors. In one embodiment, shared resources—such as memory, registers, and caches—may be accessible to multiple virtual processors within a given core 502. In other embodiments, shared resources may be accessible to multiple processing entities within processor 500.

Cache hierarchy 503 may be implemented in any suitable manner. For example, cache hierarchy 503 may include one or more lower or mid-level caches, such as caches 572, 574. In one embodiment, cache hierarchy 503 may include an LLC 595 communicatively coupled to caches 572, 574 through logic block 576. In another embodiment, LLC 595 may be implemented in a module 590 accessible to all processing entities of processor 500. In a further embodiment, module 590 may be implemented in an uncore module of processors from Intel, Inc. Module 590 may include portions or subsystems of processor 500 necessary for the execution of core 502 but might not be implemented within core 502. Besides LLC 595, Module 590 may include, for example, hardware interfaces, memory coherency coordinators, interprocessor interconnects, instruction pipelines, or memory controllers. Access to RAM 599 available to processor 500 may be made through module 590 and, more specifically, LLC 595. Furthermore, other instances of core 502 may similarly access module 590. Coordination of the instances of core 502 may be facilitated in part through module 590.

FIGS. 6-8 may illustrate exemplary systems suitable for including processor 500, while FIG. 9 may illustrate an exemplary system on a chip (SoC) that may include one or more of cores 502. Other system designs and implementations known in the arts for laptops, desktops, handheld PCs, personal digital assistants, engineering workstations, servers, network devices, network hubs, switches, embedded processors, digital signal processors (DSPs), graphics devices, video game devices, set-top boxes, micro controllers, cell phones, portable media players, hand held devices, and various other electronic devices, may also be suitable. In general, a huge variety of systems or electronic devices that incorporate a processor and/or other execution logic as disclosed herein may be generally suitable.

FIG. 6 illustrates a block diagram of a system 600, in accordance with embodiments of the present disclosure. System 600 may include one or more processors 610, 615, which may be coupled to graphics memory controller hub (GMCH) 620. The optional nature of additional processors 615 is denoted in FIG. 6 with broken lines.

Each processor 610,615 may be some version of processor 500. However, it should be noted that integrated graphics logic and integrated memory control units might not exist in processors 610,615. FIG. 6 illustrates that GMCH 620 may be coupled to a memory 640 that may be, for example, a dynamic random access memory (DRAM). The DRAM may, for at least one embodiment, be associated with a non-volatile cache.

GMCH 620 may be a chipset, or a portion of a chipset. GMCH 620 may communicate with processors 610, 615 and control interaction between processors 610, 615 and memory 640. GMCH 620 may also act as an accelerated bus interface between the processors 610, 615 and other elements of system 600. In one embodiment, GMCH 620 communicates with processors 610, 615 via a multi-drop bus, such as a frontside bus (FSB) 695.

Furthermore, GMCH 620 may be coupled to a display 645 (such as a flat panel display). In one embodiment, GMCH 620 may include an integrated graphics accelerator. GMCH 620 may be further coupled to an input/output (I/O) controller hub (ICH) 650, which may be used to couple various peripheral devices to system 600. External graphics device 660 may include a discrete graphics device coupled to ICH 650 along with another peripheral device 670.

In other embodiments, additional or different processors may also be present in system 600. For example, additional processors 610, 615 may include additional processors that may be the same as processor 610, additional processors that may be heterogeneous or asymmetric to processor 610, accelerators (such as, e.g., graphics accelerators or digital signal processing (DSP) units), field programmable gate arrays, or any other processor. There may be a variety of differences between the physical resources 610, 615 in terms of a spectrum of metrics of merit including architectural, micro-architectural, thermal, power consumption characteristics, and the like. These differences may effectively manifest themselves as asymmetry and heterogeneity amongst processors 610, 615. For at least one embodiment, various processors 610, 615 may reside in the same die package.

FIG. 7 illustrates a block diagram of a second system 700, in accordance with embodiments of the present disclosure. As shown in FIG. 7, multiprocessor system 700 may include a point-to-point interconnect system, and may include a first processor 770 and a second processor 780 coupled via a point-to-point interconnect 750. Each of processors 770 and 780 may be some version of processor 500 as one or more of processors 610,615.

While FIG. 7 may illustrate two processors 770, 780, it is to be understood that the scope of the present disclosure is not so limited. In other embodiments, one or more additional processors may be present in a given processor.

Processors 770 and 780 are shown including integrated memory controller units 772 and 782, respectively. Processor 770 may also include as part of its bus controller units point-to-point (P-P) interfaces 776 and 778; similarly, second processor 780 may include P-P interfaces 786 and 788. Processors 770, 780 may exchange information via a point-to-point (P-P) interface 750 using P-P interface circuits 778, 788. As shown in FIG. 7, IMCs 772 and 782 may couple the processors to respective memories, namely a memory 732 and a memory 734, which in one embodiment may be portions of main memory locally attached to the respective processors.

Processors 770, 780 may each exchange information with a chipset 790 via individual P-P interfaces 752, 754 using point to point interface circuits 776, 794, 786, 798. In one embodiment, chipset 790 may also exchange information with a high-performance graphics circuit 738 via interface 792 over a high-performance graphics bus 739.

A shared cache (not shown) may be included in either processor or outside of both processors, yet connected with the processors via P-P interconnect, such that either or both processors' local cache information may be stored in the shared cache if a processor is placed into a low power mode.

Chipset 790 may be coupled to a first bus 716 via an interface 796. In one embodiment, first bus 716 may be a Peripheral Component Interconnect (PCI) bus, or a bus such as a PCI Express bus or another third generation I/O interconnect bus, although the scope of the present disclosure is not so limited.

As shown in FIG. 7, various I/O devices 714 may be coupled to first bus 716, along with a bus bridge 718 which couples first bus 716 to a second bus 720. In one embodiment, second bus 720 may be a low pin count (LPC) bus. Various devices may be coupled to second bus 720 including, for example, a keyboard and/or mouse 722, communication devices 727 and a storage unit 728 such as a disk drive or other mass storage device which may include instructions/code and data 730, in one embodiment. Further, an audio I/O 724 may be coupled to second bus 720. Note that other architectures may be possible. For example, instead of the point-to-point architecture of FIG. 7, a system may implement a multi-drop bus or other such architecture.

FIG. 8 illustrates a block diagram of a third system 800 in accordance with embodiments of the present disclosure. Like elements in FIGS. 7 and 8 bear like reference numerals, and certain aspects of FIG. 7 have been omitted from FIG. 8 in order to avoid obscuring other aspects of FIG. 8.

FIG. 8 illustrates that processors 770, 780 may include integrated memory and I/O control logic (“CL”) 872 and 882, respectively. For at least one embodiment, CL 872, 882 may include integrated memory controller units such as that described above in connection with FIGS. 5 and 7. In addition. CL 872, 882 may also include I/O control logic. FIG. 8 illustrates that not only memories 732, 734 may be coupled to CL 872, 882, but also that I/O devices 814 may also be coupled to control logic 872, 882. Legacy I/O devices 815 may be coupled to chipset 790.

FIG. 9 illustrates a block diagram of a SoC 900, in accordance with embodiments of the present disclosure. Similar elements in FIG. 5 bear like reference numerals. Also, dashed lined boxes may represent optional features on more advanced SoCs. An interconnect units 902 may be coupled to: an application processor 910 which may include a set of one or more cores 502A-N, including respective local caches 504A-N, and shared cache units 506; a system agent unit 510; a bus controller units 916; an integrated memory controller units 914; a set of one or more media processors 920 which may include integrated graphics logic 908, an image processor 924 for providing still and/or video camera functionality, an audio processor 926 for providing hardware audio acceleration, and a video processor 928 for providing video encode/decode acceleration; an static random access memory (SRAM) unit 930; a direct memory access (DMA) unit 932; and a display unit 940 for coupling to one or more external displays.

FIG. 10 illustrates a processor containing a central processing unit (CPU) and a graphics processing unit (GPU), which may perform at least one instruction, in accordance with embodiments of the present disclosure. In one embodiment, an instruction to perform operations according to at least one embodiment could be performed by the CPU. In another embodiment, the instruction could be performed by the GPU. In still another embodiment, the instruction may be performed through a combination of operations performed by the GPU and the CPU. For example, in one embodiment, an instruction in accordance with one embodiment may be received and decoded for execution on the GPU. However, one or more operations within the decoded instruction may be performed by a CPU and the result returned to the GPU for final retirement of the instruction. Conversely, in some embodiments, the CPU may act as the primary processor and the GPU as the co-processor.

In some embodiments, instructions that benefit from highly parallel, throughput processors may be performed by the GPU, while instructions that benefit from the performance of processors that benefit from deeply pipelined architectures may be performed by the CPU. For example, graphics, scientific applications, financial applications and other parallel workloads may benefit from the performance of the GPU and be executed accordingly, whereas more sequential applications, such as operating system kernel or application code may be better suited for the CPU.

In FIG. 10, processor 1000 includes a CPU 1005, GPU 1010, image processor 1015, video processor 1020, USB controller 1025, UART controller 1030, SPI/SDIO controller 1035, display device 1040, memory interface controller 1045, MIPI controller 1050, flash memory controller 1055, dual data rate (DDR) controller 1060, security engine 1065, and I²S/I²C controller 1070. Other logic and circuits may be included in the processor of FIG. 10, including more CPUs or GPUs and other peripheral interface controllers.

One or more aspects of at least one embodiment may be implemented by representative data stored on a machine-readable medium which represents various logic within the processor, which when read by a machine causes the machine to fabricate logic to perform the techniques described herein. Such representations, known as “IP cores” may be stored on a tangible, machine-readable medium (“tape”) and supplied to various customers or manufacturing facilities to load into the fabrication machines that actually make the logic or processor. For example, IP cores, such as the Cortex™ family of processors developed by ARM Holdings, Ltd. and Loongson IP cores developed the Institute of Computing Technology (ICT) of the Chinese Academy of Sciences may be licensed or sold to various customers or licensees, such as Texas Instruments, Qualcomm, Apple, or Samsung and implemented in processors produced by these customers or licensees.

FIG. 11 illustrates a block diagram illustrating the development of IP cores, in accordance with embodiments of the present disclosure. Storage 1100 may include simulation software 1120 and/or hardware or software model 1110. In one embodiment, the data representing the IP core design may be provided to storage 1100 via memory 1140 (e.g., hard disk), wired connection (e.g., internet) 1150 or wireless connection 1160. The IP core information generated by the simulation tool and model may then be transmitted to a fabrication facility 1165 where it may be fabricated by a 3^(rd) party to perform at least one instruction in accordance with at least one embodiment.

In some embodiments, one or more instructions may correspond to a first type or architecture (e.g., x86) and be translated or emulated on a processor of a different type or architecture (e.g., ARM). An instruction, according to one embodiment, may therefore be performed on any processor or processor type, including ARM, x86, MIPS, a GPU, or other processor type or architecture.

FIG. 12 illustrates how an instruction of a first type may be emulated by a processor of a different type, in accordance with embodiments of the present disclosure. In FIG. 12, program 1205 contains some instructions that may perform the same or substantially the same function as an instruction according to one embodiment. However the instructions of program 1205 may be of a type and/or format that is different from or incompatible with processor 1215, meaning the instructions of the type in program 1205 may not be able to execute natively by the processor 1215. However, with the help of emulation logic, 1210, the instructions of program 1205 may be translated into instructions that may be natively be executed by the processor 1215. In one embodiment, the emulation logic may be embodied in hardware. In another embodiment, the emulation logic may be embodied in a tangible, machine-readable medium containing software to translate instructions of the type in program 1205 into the type natively executable by processor 1215. In other embodiments, emulation logic may be a combination of fixed-function or programmable hardware and a program stored on a tangible, machine-readable medium. In one embodiment, the processor contains the emulation logic, whereas in other embodiments, the emulation logic exists outside of the processor and may be provided by a third party. In one embodiment, the processor may load the emulation logic embodied in a tangible, machine-readable medium containing software by executing microcode or firmware contained in or associated with the processor.

FIG. 13 illustrates a block diagram contrasting the use of a software instruction converter to convert binary instructions in a source instruction set to binary instructions in a target instruction set, in accordance with embodiments of the present disclosure. In the illustrated embodiment, the instruction converter may be a software instruction converter, although the instruction converter may be implemented in software, firmware, hardware, or various combinations thereof. FIG. 13 shows a program in a high level language 1302 may be compiled using an x86 compiler 1304 to generate x86 binary code 1306 that may be natively executed by a processor with at least one x86 instruction set core 1316. The processor with at least one x86 instruction set core 1316 represents any processor that may perform substantially the same functions as an Intel processor with at least one x86 instruction set core by compatibly executing or otherwise processing (1) a substantial portion of the instruction set of the Intel x86 instruction set core or (2) object code versions of applications or other software targeted to run on an Intel processor with at least one x86 instruction set core, in order to achieve substantially the same result as an Intel processor with at least one x86 instruction set core. x86 compiler 1304 represents a compiler that may be operable to generate x86 binary code 1306 (e.g., object code) that may, with or without additional linkage processing, be executed on the processor with at least one x86 instruction set core 1316. Similarly, FIG. 13 shows the program in high level language 1302 may be compiled using an alternative instruction set compiler 1308 to generate alternative instruction set binary code 1310 that may be natively executed by a processor without at least one x86 instruction set core 1314 (e.g., a processor with cores that execute the MIPS instruction set of MIPS Technologies of Sunnyvale, CA and/or that execute the ARM instruction set of ARM Holdings of Sunnyvale, Calif.). Instruction converter 1312 may be used to convert x86 binary code 1306 into code that may be natively executed by the processor without an x86 instruction set core 1314. This converted code might not be the same as alternative instruction set binary code 1310; however, the converted code will accomplish the general operation and be made up of instructions from the alternative instruction set. Thus, instruction converter 1312 represents software, firmware, hardware, or a combination thereof that, through emulation, simulation or any other process, allows a processor or other electronic device that does not have an x86 instruction set processor or core to execute x86 binary code 1306.

FIG. 14 is a block diagram of an instruction set architecture 1400 of a processor, in accordance with embodiments of the present disclosure. Instruction set architecture 1400 may include any suitable number or kind of components.

For example, instruction set architecture 1400 may include processing entities such as one or more cores 1406, 1407 within a processor subsystem 1405, and a graphics processing unit 1415. Cores 1406, 1407 may be communicatively coupled to the rest of instruction set architecture 1400 through any suitable mechanism, such as through a bus or cache. In one embodiment, cores 1406, 1407 may be communicatively coupled through an L2 cache control 1408, which may include a bus interface unit 1409 and an L2 cache 1411. Cores 1406, 1407 and graphics processing unit 1415 may be communicatively coupled to each other and to the remainder of instruction set architecture 1400 through interconnect 1410. In one embodiment, graphics processing unit 1415 may use a video codec 1420 defining the manner in which particular video signals will be encoded and decoded for output.

Instruction set architecture 1400 may also include any number or kind of interfaces, controllers, or other mechanisms for interfacing or communicating with other portions of an electronic device or system. Such mechanisms may facilitate interaction with, for example, peripherals, communications devices, other processors, or memory. In the example of FIG. 14, instruction set architecture 1400 may include a liquid crystal display (LCD) video interface 1425, a subscriber interface module (SIM) interface 1430, a boot ROM interface 1435, a synchronous dynamic random access memory (SDRAM) controller 1440, a flash controller 1445, and a serial peripheral interface (SPI) master unit 1450. LCD video interface 1425 may provide output of video signals from, for example, GPU 1415 and through, for example, a mobile industry processor interface (MIPI) 1490 or a high-definition multimedia interface (HDMI) 1495 to a display. Such a display may include, for example, an LCD. SIM interface 1430 may provide access to or from a SIM card or device. SDRAM controller 1440 may provide access to or from memory such as an SDRAM chip or module 1460. Flash controller 1445 may provide access to or from memory such as flash memory 1465 or other instances of RAM. SPI master unit 1450 may provide access to or from communications modules, such as a Bluetooth module 1470, high-speed 3G modem 1475, global positioning system module 1480, or wireless module 1485 implementing a communications standard such as 802.11. Instruction set architecture 1400 may also include a power control unit 1455.

FIG. 15 is a more detailed block diagram of an instruction set architecture 1500 of a processor, in accordance with embodiments of the present disclosure. Instruction architecture 1500 may implement one or more aspects of instruction set architecture 1400. Furthermore, instruction set architecture 1500 may illustrate modules and mechanisms for the execution of instructions within a processor.

Instruction architecture 1500 may include a memory system 1540 communicatively coupled to one or more execution entities 1565. Furthermore, instruction architecture 1500 may include a caching and bus interface unit such as unit 1510 communicatively coupled to execution entities 1565 and memory system 1540. In one embodiment, loading of instructions into execution entities 1565 may be performed by one or more stages of execution. Such stages may include, for example, instruction prefetch stage 1530, dual instruction decode stage 1550, register rename stage 1555, issue stage 1560, and writeback stage 1570.

In one embodiment, memory system 1540 may include an executed instruction pointer 1580. Executed instruction pointer 1580 may store a value identifying the oldest, undispatched instruction within a batch of instructions. The oldest instruction may correspond to the lowest Program Order (PO) value. A PO may include a unique number of an instruction. Such an instruction may be a single instruction within a thread represented by multiple strands. A PO may be used in ordering instructions to ensure correct execution semantics of code. A PO may be reconstructed by mechanisms such as evaluating increments to PO encoded in the instruction rather than an absolute value. Such a reconstructed PO may be known as an “RPO.” Although a PO may be referenced herein, such a PO may be used interchangeably with an RPO. A strand may include a sequence of instructions that are data dependent upon each other. The strand may be arranged by a binary translator at compilation time. Hardware executing a strand may execute the instructions of a given strand in order according to the PO of the various instructions. A thread may include multiple strands such that instructions of different strands may depend upon each other. A PO of a given strand may be the PO of the oldest instruction in the strand which has not yet been dispatched to execution from an issue stage. Accordingly, given a thread of multiple strands, each strand including instructions ordered by PO, executed instruction pointer 1580 may store the oldest—illustrated by the lowest number—PO in the thread.

In another embodiment, memory system 1540 may include a retirement pointer 1582. Retirement pointer 1582 may store a value identifying the PO of the last retired instruction. Retirement pointer 1582 may be set by, for example, retirement unit 454. If no instructions have yet been retired, retirement pointer 1582 may include a null value.

Execution entities 1565 may include any suitable number and kind of mechanisms by which a processor may execute instructions. In the example of FIG. 15, execution entities 1565 may include ALU/multiplication units (MUL) 1566, ALUs 1567, and floating point units (FPU) 1568. In one embodiment, such entities may make use of information contained within a given address 1569. Execution entities 1565 in combination with stages 1530, 1550, 1555, 1560, 1570 may collectively form an execution unit.

Unit 1510 may be implemented in any suitable manner. In one embodiment, unit 1510 may perform cache control. In such an embodiment, unit 1510 may thus include a cache 1525. Cache 1525 may be implemented, in a further embodiment, as an L2 unified cache with any suitable size, such as zero, 128k, 256k, 512k, 1M, or 2M bytes of memory. In another, further embodiment, cache 1525 may be implemented in error-correcting code memory. In another embodiment, unit 1510 may perform bus interfacing to other portions of a processor or electronic device. In such an embodiment, unit 1510 may thus include a bus interface unit 1520 for communicating over an interconnect, intraprocessor bus, interprocessor bus, or other communication bus, port, or line. Bus interface unit 1520 may provide interfacing in order to perform, for example, generation of the memory and input/output addresses for the transfer of data between execution entities 1565 and the portions of a system external to instruction architecture 1500.

To further facilitate its functions, bus interface unit 1510 may include an interrupt control and distribution unit 1511 for generating interrupts and other communications to other portions of a processor or electronic device. In one embodiment, bus interface unit 1510 may include a snoop control unit 1512 that handles cache access and coherency for multiple processing cores. In a further embodiment, to provide such functionality, snoop control unit 1512 may include a cache-to-cache transfer unit 1513 that handles information exchanges between different caches. In another, further embodiment, snoop control unit 1512 may include one or more snoop filters 1514 that monitors the coherency of other caches (not shown) so that a cache controller, such as unit 1510, does not have to perform such monitoring directly. Unit 1510 may include any suitable number of timers 1515 for synchronizing the actions of instruction architecture 1500. Also, unit 1510 may include an AC port 1516.

Memory system 1540 may include any suitable number and kind of mechanisms for storing information for the processing needs of instruction architecture 1500. In one embodiment, memory system 1540 may include a load store unit 1546 for storing information such as buffers written to or read back from memory or registers and a data cache 1542. In another embodiment, memory system 1540 may include a translation lookaside buffer (TLB) 1545 that provides look-up of address values between physical and virtual addresses. In yet another embodiment, memory system 1540 may include a memory management unit (MMU) 1544 for facilitating access to virtual memory. In still yet another embodiment, memory system 1540 may include a prefetcher 1543 for requesting instructions from memory before such instructions are actually needed to be executed, in order to reduce latency.

The operation of instruction architecture 1500 to execute an instruction may be performed through different stages. For example, using unit 1510 instruction prefetch stage 1530 may access an instruction through prefetcher 1543. Instructions retrieved may be stored in instruction cache 1532. Prefetch stage 1530 may enable an option 1531 for fast-loop mode, wherein a series of instructions forming a loop that is small enough to fit within a given cache are executed. In one embodiment, such an execution may be performed without needing to access additional instructions from, for example, instruction cache 1532. Determination of what instructions to prefetch may be made by, for example, branch prediction unit 1535, which may access indications of execution in global history 1536, indications of target addresses 1537, or contents of a return stack 1538 to determine which of branches 1557 of code will be executed next. Such branches may be possibly prefetched as a result. Branches 1557 may be produced through other stages of operation as described below. Instruction prefetch stage 1530 may provide instructions as well as any predictions about future instructions to dual instruction decode stage 1550.

Dual instruction decode stage 1550 may translate a received instruction into microcode-based instructions that may be executed. Dual instruction decode stage 1550 may simultaneously decode two instructions per clock cycle. Furthermore, dual instruction decode stage 1550 may pass its results to register rename stage 1555. In addition, dual instruction decode stage 1550 may determine any resulting branches from its decoding and eventual execution of the microcode. Such results may be input into branches 1557.

Register rename stage 1555 may translate references to virtual registers or other resources into references to physical registers or resources. Register rename stage 1555 may include indications of such mapping in a register pool 1556. Register rename stage 1555 may alter the instructions as received and send the result to issue stage 1560.

Issue stage 1560 may issue or dispatch commands to execution entities 1565. Such issuance may be performed in an out-of-order fashion. In one embodiment, multiple instructions may be held at issue stage 1560 before being executed. Issue stage 1560 may include an instruction queue 1561 for holding such multiple commands. Instructions may be issued by issue stage 1560 to a particular processing entity 1565 based upon any acceptable criteria, such as availability or suitability of resources for execution of a given instruction. In one embodiment, issue stage 1560 may reorder the instructions within instruction queue 1561 such that the first instructions received might not be the first instructions executed. Based upon the ordering of instruction queue 1561, additional branching information may be provided to branches 1557. Issue stage 1560 may pass instructions to executing entities 1565 for execution.

Upon execution, writeback stage 1570 may write data into registers, queues, or other structures of instruction set architecture 1500 to communicate the completion of a given command. Depending upon the order of instructions arranged in issue stage 1560, the operation of writeback stage 1570 may enable additional instructions to be executed. Performance of instruction set architecture 1500 may be monitored or debugged by trace unit 1575.

FIG. 16 is a block diagram of an execution pipeline 1600 for an instruction set architecture of a processor, in accordance with embodiments of the present disclosure. Execution pipeline 1600 may illustrate operation of, for example, instruction architecture 1500 of FIG. 15.

Execution pipeline 1600 may include any suitable combination of operations. In 1605, predictions of the branch that is to be executed next may be made. In one embodiment, such predictions may be based upon previous executions of instructions and the results thereof. In 1610, instructions corresponding to the predicted branch of execution may be loaded into an instruction cache. In 1615, one or more such instructions in the instruction cache may be fetched for execution. In 1620, the instructions that have been fetched may be decoded into microcode or more specific machine language. In one embodiment, multiple instructions may be simultaneously decoded. In 1625, references to registers or other resources within the decoded instructions may be reassigned. For example, references to virtual registers may be replaced with references to corresponding physical registers. In 1630, the instructions may be dispatched to queues for execution. In 1640, the instructions may be executed. Such execution may be performed in any suitable manner. In 1650, the instructions may be issued to a suitable execution entity. The manner in which the instruction is executed may depend upon the specific entity executing the instruction. For example, at 1655, an ALU may perform arithmetic functions. The ALU may utilize a single clock cycle for its operation, as well as two shifters. In one embodiment, two ALUs may be employed, and thus two instructions may be executed at 1655. At 1660, a determination of a resulting branch may be made. A program counter may be used to designate the destination to which the branch will be made. 1660 may be executed within a single clock cycle. At 1665, floating point arithmetic may be performed by one or more FPUs. The floating point operation may require multiple clock cycles to execute, such as two to ten cycles. At 1670, multiplication and division operations may be performed. Such operations may be performed in four clock cycles. At 1675, loading and storing operations to registers or other portions of pipeline 1600 may be performed. The operations may include loading and storing addresses. Such operations may be performed in four clock cycles. At 1680, write-back operations may be performed as required by the resulting operations of 1655-1675.

FIG. 17 is a block diagram of an electronic device 1700 for utilizing a processor 1710, in accordance with embodiments of the present disclosure. Electronic device 1700 may include, for example, a notebook, an ultrabook, a computer, a tower server, a rack server, a blade server, a laptop, a desktop, a tablet, a mobile device, a phone, an embedded computer, or any other suitable electronic device.

Electronic device 1700 may include processor 1710 communicatively coupled to any suitable number or kind of components, peripherals, modules, or devices. Such coupling may be accomplished by any suitable kind of bus or interface, such as I²C bus, system management bus (SMBus), low pin count (LPC) bus, SPI, high definition audio (HDA) bus, Serial Advance Technology Attachment (SATA) bus, USB bus (versions 1, 2, 3), or Universal Asynchronous Receiver/Transmitter (UART) bus.

Such components may include, for example, a display 1724, a touch screen 1725, a touch pad 1730, a near field communications (NFC) unit 1745, a sensor hub 1740, a thermal sensor 1746, an express chipset (EC) 1735, a trusted platform module (TPM) 1738, BIOS/firmware/flash memory 1722, a digital signal processor 1760, a drive 1720 such as a solid state disk (SSD) or a hard disk drive (HDD), a wireless local area network (WLAN) unit 1750, a Bluetooth unit 1752, a wireless wide area network (WWAN) unit 1756, a global positioning system (GPS) 1755, a camera 1754 such as a USB 3.0 camera, or a low power double data rate (LPDDR) memory unit 1715 implemented in, for example, the LPDDR3 standard. These components may each be implemented in any suitable manner.

Furthermore, in various embodiments other components may be communicatively coupled to processor 1710 through the components discussed above. For example, an accelerometer 1741, ambient light sensor (ALS) 1742, compass 1743, and gyroscope 1744 may be communicatively coupled to sensor hub 1740. A thermal sensor 1739, fan 1737, keyboard 1736, and touch pad 1730 may be communicatively coupled to EC 1735. Speakers 1763, headphones 1764, and a microphone 1765 may be communicatively coupled to an audio unit 1762, which may in turn be communicatively coupled to DSP 1760. Audio unit 1762 may include, for example, an audio codec and a class D amplifier. A SIM card 1757 may be communicatively coupled to WWAN unit 1756. Components such as WLAN unit 1750 and Bluetooth unit 1752, as well as WWAN unit 1756 may be implemented in a next generation form factor (NGFF).

Embodiments of the present disclosure involve hardware circuitry or logic for implementing cache replacement using conservative set dueling. FIG. 18 is an illustration of an example system 1800 including a cache controller for conservative set dueling for cache replacement, according to embodiments of the present disclosure. The cache controller may include hardware circuitry or logic to perform cache replacement for a set associative cache in accordance with multiple cache replacement policies, each of which may specify a respective cache line insertion policy and a respective cache line eviction policy. Some cache replacement policies may specify that each cache line is to be inserted into the cache in a manner that delays its eligibility for eviction from the set associative cache. For example, the cache replacement policy may specify that each cache line is to be inserted into the cache such that it is treated as the most recently used (MRU) cache line and is, therefore, not currently eligible for eviction. These types of cache replacement policies may be well suited for the insertion of data that is likely to be reused. Other cache replacement policies may specify that each cache line is to be inserted into the cache in a manner that makes it eligible for eviction from the set associative cache. For example, the cache replacement policy may specify that each cache line is to be inserted into the cache such that it is treated as the least recently used (LRU) cache line and is, therefore, immediately eligible for eviction. These types of cache replacement policies may be well suited for the insertion of data that is not likely to be reused, such as data that is streamed through the processor only once.

In at least some embodiments of the present disclosure, system 1800 may apply different cache replacement policies at different times and for different groups of cache lines in a set associative cache based on the results conservative set dueling, as described herein. For example, system 1800 may include a cache that stores data in a plurality of cache lines organized in groups of sets dependent on the respective index values associated with each of the cache lines. Using an existing set dueling approach, a cache controller may assign each of two different cache replacement policies to a different, and very small, dedicated group of sets and may determine which of these policies is to be applied to the majority of the sets based on the relative performance of the policies over the dedicated groups of sets. In one example, a first cache replacement policy may be assigned to a first group of sets that includes on the order of 1% to 3% of the sets in the cache, and a second cache replacement policy may be assigned to a second, non-overlapping group of sets of approximately the same size in the cache. In this example, a counter that is initialized to its midpoint value may be decremented each time there is a cache miss for a cache line in the second group of sets and may be incremented each time there is a cache miss for a cache line in the first group of sets. The cache replacement policy for the remaining sets, which are sometimes referred to as “follower sets” may be determined at any given time based on the instantaneous value of the counter. In one example, if the value of the counter is above the midpoint value for the counter, cache lines in the follower sets may be inserted using the first cache replacement policy. Conversely, if the value of the counter is below the midpoint value for the counter, cache lines in the follower sets may be inserted using the second cache replacement policy. With this existing set dueling approach, the groups of sets to which each cache replacement policy is applied does not change during operation of the system. This can make the result of the set dueling sensitive to the choice of sampled sets included in each of the dedicated groups of sets. For example, if the sampled sets do not happen to be representative of the majority of the program behavior, then this existing set dueling approach might select a policy that is suboptimal for the follower sets.

In embodiments of the present disclosure, system 1800 may include hardware circuitry or logic to perform cache line insertion using conservative set dueling to determine the cache replacement policy to be used for the follower sets. For example, in at least some embodiments, system 1800 may extend a 1-bit Not Recently Used (NRU) cache to apply an Adaptive Fill Policy (AFP). Unlike in existing set dueling approaches, in which each of two cache replacement schemes is applied to a respective dedicated group of sample sets and the relative performance of the two schemes is continuously evaluated, system 1800 may include hardware circuitry or logic to rotate the groups of sets involved in set dueling at the end of discrete rounds of experimentation, swapping the cache replacement schemes that are applied to the groups of sets. In at least some embodiments, system 1800 may also include a mechanism to make it less likely for a stream resistant policy to be chosen for the follower sets by set dueling in circumstances in which it would harm performance. In some embodiments, system 1800 may include hardware circuitry or logic that makes it less likely for this to happen by requiring relatively higher risk cache replacement policies to be tested in multiple groups of sampled sets before the follower sets adopt them. For example, in some embodiments, higher risk cache replacement policies may be required to “win” more successive rounds of experimentation than more conservative cache replacement policies in order for follower sets to use the policy. This conservative approach to selecting a cache replacement policy for the follower sets may lower the chance that a suboptimal, harmful cache management policy is chosen for the follower sets.

System 1800 may include a processor, SoC, integrated circuit, or other mechanism. For example, system 1800 may include processor core 1804. Although processor core 1804 is shown and described as an example in FIG. 18, any suitable mechanism may be used. Processor core 1804 may include any suitable mechanisms for cache line eviction and cache line insertion, including those that perform conservative set dueling to determine the cache replacement policy to be used for follower sets. In one embodiment, such mechanisms may be implemented in hardware. Processor core 1804 may be implemented fully or in part by the elements described in FIGS. 1-17.

Instructions to be executed on processor core 1804 may be included in instruction stream 1802. Instruction stream 1802 may be generated by, for example, a compiler, just-in-time interpreter, or other suitable mechanism (which might or might not be included in system 1800), or may be designated by a drafter of code resulting in instruction stream 1802. For example, a compiler may take application code and generate executable code in the form of instruction stream 1802. Instructions may be received by processor core 1804 from instruction stream 1802. Instruction stream 1802 may be loaded to processor core 1804 in any suitable manner. For example, instructions to be executed by processor core 1804 may be loaded from storage, from other machines, or from other memory, such as memory system 1850. The instructions may arrive and be available in resident memory, such as RAM, and may be fetched from storage to be executed by processor core 1804. The instructions may be fetched from resident memory by, for example, a prefetcher or fetch unit (such as instruction fetch unit 1808).

Processor core 1804 may include a front end 1806 and a back end 1812. Front end 1806 may include an instruction fetch pipeline stage (such as instruction fetch unit 1808) and a decode pipeline stage (such as decide unit 1810). Front end 1806 may receive and decode instructions from instruction stream 1802 using decode unit 1810. The decoded instructions may be dispatched, allocated, and scheduled for execution by an allocation stage of back end 1812 (such as allocator 1814) and allocated to specific execution units 1816 within back end 1812 for execution. One or more specific instructions to be executed by processor core 1804 may be included in a library defined for execution by processor core 1804. In another embodiment, specific instructions may be targeted by particular portions of processor core 1804. For example, processor core 1804 may recognize an attempt in instruction stream 1802 to execute a vector operation in software and may issue the instruction to a particular one of execution units 1816 to execute the instruction.

During execution, access to data or additional instructions (including data or instructions resident in memory system 1850) may be made through memory subsystem 1820. Moreover, results from execution may be stored in memory subsystem 1820 and may subsequently be flushed to memory system 1850. Memory subsystem 1820 may include, for example, memory, RAM, or a cache hierarchy, which may include one or more Level 1 (L1) caches 1822 or Level 2 (L2) caches 1824, some of which may be shared by multiple processor cores 1804. In other embodiments, one or more caches or cache units may be internal to a core, external to a core, or apportioned internal to and external to a core in different combinations. After execution by execution units 1816, instructions may be retired by a writeback stage or retirement stage in retirement unit 1830 within back end 1812.

Memory subsystem 1820 may also include a cache controller 1826. Cache controller 1826 may control the assignment of various L1 caches 1822 and L2 caches 1824 for the use of execution units 1816 within back end 1812. In at least some embodiments, cache controller 1826 may include hardware circuitry or logic to control the insertion of cache lines into the L1 caches 1822 and L2 caches 1824 and the eviction of cache lines from the L1 caches 1822 and L2 caches 1824 in accordance with one or more cache replacement policies for the caches. For example, at any given time, cache controller 1826 may apply a first cache replacement policy to a first portion of one of the caches and may apply a second cache replacement policy to one or more other portions of the same cache or to all or a portion of another one of the caches. In some embodiments, cache controller 1826 may include hardware circuitry or logic to determine the insertion policy by which cache lines are to be inserted into the caches, or into particular portions thereof, using the conservative set dueling approach described herein.

In at least some embodiments of the present disclosure, the selection of sets to be included in each of the two groups of sets involved in set dueling may be performed randomly or pseudo randomly, and in a manner that ensures that the two group sets of sets are non-overlapping. In some embodiments, the selection of the sets to be included in each of the two groups of sets may be made at design time and may not change during operation. However, the cache replacement policies associated with each of the two groups of sets may change from time to time during operation. In some embodiments, by randomly selecting the sets to be included in each of the groups of sets, the groups of sets may be as statistically representative of the average behavior of the cache as possible. In one example, a first randomly selected 1% of the sets may initially be designated to use a first cache replacement policy and a second randomly selected 1% of the sets may initially be designated to use a second cache replacement policy. In at least some embodiments, the systems described herein may, in response to detecting a condition indicating that the associations between the two groups of sets and the two cache replacement policies should be swapped, update the associations so that the first randomly selected 1% of the sets is designated to use the second cache replacement policy and the second randomly selected 1% of the sets is designated to use the first cache replacement policy. In one example, these associations may be swapped after a predetermined amount of time that defines a set dueling epoch. In another example, the associations may be swapped based on detection of a performance-related threshold condition that defines a set dueling epoch.

FIG. 19 is an illustration of an example method 1900 for implementing cache replacement using set dueling with set swapping, according to embodiments of the present disclosure. Method 1900 may be implemented by any of the elements shown in FIGS. 1-18. Method 1900 may be initiated by any suitable criteria and may initiate operation at any suitable point. In one embodiment, method 1900 may initiate operation at 1905. Method 1900 may include greater or fewer operations than those illustrated. Moreover, method 1900 may execute its operations in an order different than those illustrated below. Method 1900 may terminate at any suitable operation. Moreover, method 1900 may repeat operation at any suitable operation. Method 1900 may perform any of its operations in parallel with other operations of method 1900, or in parallel with operations of other methods.

Furthermore, method 1900 may be executed multiple times to determine when and whether to update the cache replacement policies applied to different groups of sets in a set associative cache or in multiple set associative caches. Method 1900 may be executed over time to update the cache replacement policies applied to a set associative cache, or to portions thereof, in response to changing workloads or other conditions. Based upon the results of method 1900, other methods may be invoked, such as method 2200 described below. These additional methods may be invoked during the execution of method 1900 to perform some of the operations of method 1900.

At 1905, in one embodiment, a first cache replacement policy is associated with a first group of sets of a set associative cache in a processor. Each set in the first group of sets may be identified by respective index bit(s) for the set. The first group of sets may include a relatively small sample of the sets of the cache that is to be included in the set dueling process to determine the cache replacement policy to be applied to follower sets in the cache.

At 1910, a second cache replacement policy is associated with a second group of sets of the set associative cache. Each set in the second group of sets may be identified by respective index bit(s) for the set. The second group of sets may include a relatively small sample of the sets of the cache that is to be included in the set dueling process to determine the cache replacement policy to be applied to follower sets in the cache. In at least some embodiments, the first group of sets and the second group of sets are non-overlapping groups of sets.

At 1915, the remaining groups of sets in the set associative cache are associated with the first cache replacement policy. Each of these follower sets may be identified by respective index bit(s) for the set. In at least some embodiments, the follower sets include all of the sets in the set associative cache that are not included in the first and second groups of sets.

At 1920, one or more cache lines are inserted into the set associative cache according to the cache replacement policies associated with the sets identified by the respective index values for the cache lines. For example, a cache line whose index value identifies it as belonging to a set in the first group of sets will be inserted into the cache in accordance with the first cache replacement policy. Similarly, a cache line whose index value identifies it as a follower set will be inserted into the cache in accordance with the first cache replacement policy. However, a cache line whose index value identifies it as belonging to a set in the second group of sets will be inserted into the cache in accordance with the second cache replacement policy.

At 1925, if a condition is detected indicating that the cache replacement policies for the first and second groups of sets should be swapped, method 1900 proceeds to 1930. Otherwise, method 1900 returns to 1920. At this point, additional cache lines may be inserted into the set associative cache using the currently associated cache replacement policies until a condition indicating that the cache replacement policies for the first and second groups of sets should be swapped is detected.

At 1930, the second group of sets is associated with the first cache replacement policy, the first group of sets is associated with second cache replacement policy, and the third group of sets (which includes the follower sets) is associated with the first cache replacement policy or the second cache replacement policy, dependent on the recent performance of the first cache replacement policy and/or the second cache replacement policy. At 1935, following the swapping of the cache replacement policies for the first and second groups of sets and the potential update to the cache replacement policy for the follower sets, cache lines are inserted into the set associative cache in accordance with the updated replacement policies associated with the sets identified by the respective index values for the cache lines.

FIG. 20 illustrates a portion of an example memory subsystem 2000 within a processor, according to embodiments of the present disclosure. In one embodiment, subsystem 2000 may include, or be a component of, memory subsystem 1820 illustrated in FIG. 18. In this example embodiment, memory subsystem 2000 includes a cache 2010 and a cache controller 2030. Cache controller 2030 includes a cache replacement unit 2020 to apply various cache insertion and cache eviction policies, as described herein. Cache controller 2030 may also include other circuitry or logic to perform other functions, such as the assignment of different caches to respective cores (not shown). In some embodiments, cache controller 2030 may control the application of suitable cache replacement policies or perform other functions for more than one cache 2010. In the example embodiment illustrated in FIG. 20, cache replacement unit 2020 includes a counter 2022 and residency control logic 2024.

The inputs to cache controller 2030 may include, but are not limited to, data 2036, tag 2034, set index 2032, and hit/miss indicator 2038. Data 2036 may include data to be written to cache 2010 or read from cache 2010 as one or more cache lines. Tag 2034 is associated with data 2036 and may represent a different respective tag for each cache line to be written to or read from cache 2010. Set index 2032 is associated with data 2036 and may represent a different respective tag for each cache line to be written to or read from cache 2010. In some embodiments, hit/miss indicator 2038 may provide cache replacement unit 2020 with information about the performance of the cache replacement policies that are applied to different groups of sets in cache 2010, such as information about cache hits and/or cache misses for cache lines having particular values of tag 2034 and set index 2032.

In at least some embodiments, cache replacement unit 2020 may include hardware circuitry or logic to associate different groups of sample sets of cache 2010 with respective cache replacement policies, to determine when and whether to swap the cache replacement policies for those groups of sample sets, to determine an initial cache replacement policy for follower sets within cache 2010, and/or to determine when and whether to change the cache replacement policy for the follower sets based on the relative performance of the cache replacement policies for the groups of sample sets. In one embodiment, cache replacement unit 2020 may include hardware circuitry or logic to increment or decrement counter 2022 in response to cache miss information for the groups of sample sets. For example, cache replacement unit 2020 may increment counter 2022 in response to an indication of a cache miss for a cache line in a first group of sample sets (one that is associated with a first cache replacement policy) and may decrement counter 2022 in response to an indication of a cache miss for a cache line in a second group of sample sets (one that is associated with a second cache replacement policy). Cache replacement unit 2020 may include hardware circuitry or logic to determine whether a cache line insertion is directed to a cache line in a particular one of the groups of sample sets or in a follower set, and thus the cache replacement policy to be applied when inserting the cache line, based on the corresponding value of set index 2032 for the cache line.

In some embodiments, cache replacement unit 2020, or residency control logic 2024 within cache replacement unit 2020, may include hardware circuitry or logic to detect the end of an epoch and to swap the cache replacement policies associated with the two groups of sample sets at the end of each epoch. In one example, detecting the end of the epoch may include determining that counter 2022 has saturated at a zero value or at its high value. In another example, detecting the end of the epoch may include determining that counter 2022 has reached a predetermined threshold value. The predetermined threshold value may represent an absolute value or a percentage of a saturation value for counter 2022. In yet another example, detecting the end of the epoch may include determining that a predetermined amount of time has passed since the cache replacement policies for the two groups of sample sets were initially assigned or were last swapped. Other criteria, such as the total number of cache misses in cache 2010 or for one or more of the groups of sample sets, or the number of cache lines written to cache 2010 or to one or more of the groups of sample sets, may be used to detect the end of each epoch, in other embodiments.

In at least some embodiments, cache replacement unit 2020 may include hardware circuitry or logic to determine, at the end of each epoch and based on the value of counter 2022 or another performance indictor, whether or not the cache replacement policy for the follower sets should also be updated. For example, residency control logic 2024 may include hardware circuitry or logic to determine that the cache replacement policy applied to the follower sets was outperformed by the other one of the two cache replacement policies implemented by cache controller 2030 during the most recent epoch. In response, residency control logic 2024 may determine that the higher performing cache replacement policy should be applied to the follower sets during at least the next epoch. In some embodiments, residency control logic 2024 may update the cache replacement policy for the follower sets from a less conservative cache replacement policy to a more conservative cache replacement policy if the less conservative cache replacement policy is outperformed by the more conservative cache replacement policy during a single epoch. In some embodiments, residency control logic 2024 may not update the cache replacement policy for the follower sets from a more conservative cache replacement policy to a less conservative cache replacement policy unless the less conservative cache replacement policy outperforms the more conservative cache replacement policy during two consecutive epochs.

In the example embodiment illustrated in FIG. 20, cache 2010 includes an array of entries 2012, each representing a respective cache line. In this example embodiment, each entry 2012 includes a field identifying the index and/or way for the entry, a tag for the entry, and the data for the cache line stored in the entry. In this example embodiment, each entry 2012 is associated with a respective NRU indicator 2014, whose value indicates whether or not the entry is considered to be a recently used entry and, therefore, whether or not it is currently eligible for eviction from cache 2010. Each NRU indicator 2014 may be implemented using a single bit or multiple bits, in different embodiments. In some embodiments, the respective NRU indicator 2014 for each entry 2012 may be resident in a field within the corresponding entry 2012 itself In other embodiments, the respective NRU indicators 2014 for all of the entries 2012 may be implemented within a separate structure within cache 2010.

In the example embodiment illustrated in FIG. 20, the outputs of cache controller 2030, or more specifically cache replacement unit 2020, may include residency control 2016, which may indicate to cache 2010 the policy with which cache lines received for insertion should be inserted into cache 2010. In one example embodiment, inserting a cache line with an NRU value of 1 may have an effect similar to the baseline operation of a cache that implements a 1-bit NRU policy, and may be similar to inserting the cache line in the “most recently used” (MRU) position in a cache that implements a Least Recently Used (LRU) cache replacement policy. Conversely, inserting a cache line with an NRU value of 0 may have an effect similar to inserting the cache line in the LRU position in a cache that implements an LRU cache replacement policy. In this example embodiment, the value of residency control 2016 may indicate whether a given cache line should be inserted with an NRU value of 0, to designate that it has not been recently used and is currently eligible for eviction, or with an NRU value of 1, to designate that it has been recently used and is not currently eligible for eviction.

While the functionality of the hardware circuitry and logic within cache controller 2030 has been described in terms of the particular structure illustrated in FIG. 20, in other embodiments, this functionality may be partitioned and/or distributed between the components of cache controller 2030 in different ways. In some embodiments, cache controller 2030 may include more, fewer, or different hardware or logic components for implementing cache replacement using conservative set dueling, as described herein. For example, the elements shown within cache replacement unit 2020 may instead be implemented in one or more other portions of cache controller 2030 or may be implemented outside of cache controller 2030.

In at least some embodiments of the present disclosure, when a cache line is reused, its NRU bit may be set to 1. However, in some embodiments, if this would result in all NRU bits in that cache set being set to 1, then all other NRU bits in that set may be changed to 0. In general, a cache line may be inserted with an NRU value of 1 if and when it is assumed that the data will be reused in the near future. On the other hand, inserting a cache line with an NRU value of 0 may be beneficial in some cases. For example, if the data in a given cache line is part of a streaming data structure that is too large to fit in the cache, it may be beneficial to insert the cache line with an NRU value of 0 so that it can be evicted quickly to make room for more streaming data. In this example, the streaming data structure may occupy a much smaller fraction of the cache, leaving more space for data that is reused or that is more likely to be reused.

FIGS. 21A and 21B illustrate the use of set dueling with set swapping for cache replacement, according to embodiments of the present disclosure. FIG. 21A illustrates an initial mapping of cache sets within a cache 2110 into different groups of sets with different cache replacement policies. In this example, two groups of sets are initially dedicated to a first cache replacement policy in which cache lines are inserted with an NRU value of 1. These groups of sets, labeled as 2112 and 2118, are shown in FIG. 21A with a crosshatched background pattern. Two other groups of sets are initially dedicated to a second cache replacement policy in which cache lines are inserted with an NRU value of 0. These groups of sets, labeled as 2114 and 2116, are shown in FIG. 21A with a densely dotted background pattern. The remaining groups of sets, including the group of sets labeled as 2121 are follower sets. In FIG. 21A, the follower sets, which are shown in FIG. 21A with no background pattern are initially associated with the first cache replacement policy in which cache lines are inserted with an NRU value of 1. In this example, the first cache replacement policy is more conservative, or less risky, of the two cache replacement policies implemented in the system. In this example, the assignments of these cache replacement policies to the identified groups of sets remain in force for at least one epoch.

In this example, the cache replacement policies for the two dedicated groups of sets are swapped at the end of each epoch, resulting in the cache replacement policy mapping shown in FIG. 21B. Specifically, the two groups of sets that were initially dedicated to the first cache replacement policy in which cache lines are inserted with an NRU value of 1 (i.e., groups 2112 and 2118) are, for the next epoch, dedicated to the second cache replacement policy in which cache lines are inserted with an NRU value of 0. Conversely, the two groups of sets that were initially dedicated to the second cache replacement policy in which cache lines are inserted with an NRU value of 0 (i.e., groups 2114 and 2116) are, for the next epoch, dedicated to the first cache replacement policy in which cache lines are inserted with an NRU value of 1.

In this example, the second cache replacement policy, which includes inserting cache lines with an NRU value of 0, resulted in better performance than the first cache replacement policy, which includes inserting cache lines with an NRU value of 1, for the most recent epoch. However, because the second cache replacement policy, which is less conservative than the first cache replacement policy, has not outperformed the first cache replacement policy for two consecutive epochs, the follower sets, including the group of sets labeled as 2121, continue to use the first cache replacement policy for the next epoch.

Unlike in some existing systems, the systems described herein may include hardware circuitry or logic to break the evaluation of two competing cache replacement policies through set dueling into discrete epochs. In some embodiments, these systems may also bias the selection process toward a preference for more conservative cache replacement policies rather than less conservative cache replacement policies. For example, the cache controller may include hardware circuitry or logic to choose a policy specifying that cache lines should be inserted with an NRU value of 1 for follower sets unless there is very strong evidence that inserting them with an NRU value of 0, which may be considered a riskier approach, is a good idea.

In some embodiments, at the end of each epoch, the cache replacement policies assigned to each of the dedicated groups of sets in the cache may be swapped and a determination of whether or not to change the cache replacement policy for the follower sets may be made. In some embodiments, each epoch may be defined as a predetermined amount of time since the current associations between the first and second groups of sets and the first and second cache replacement policies were made. In other embodiments, each epoch may be defined in terms of a performance-related threshold condition. For example, in embodiments in which a counter is used to track the relative performance of the competing cache replacement policies, detecting the end of an epoch may include determining that the value of the counter meets a predetermined threshold value. The predetermined threshold value may represent a high or low saturation value for the counter, or a predetermined percentage of a saturation value for the counter, in different embodiments. In some embodiments, the end of each epoch may be defined by a combination of time-based and/or performance-based trigger conditions. In embodiments in which a counter is used to track the relative performance of the competing cache replacement policies, the counter may be reset to an initial value, a default value, or a midpoint value between epochs.

FIG. 22 is an illustration of an example method 2200 for implementing cache replacement using conservative set dueling, according to embodiments of the present disclosure. Method 2200 may be implemented by any of the elements shown in FIGS. 1-21. Method 2200 may be initiated by any suitable criteria and may initiate operation at any suitable point. In one embodiment, method 2200 may initiate operation at 2205. Method 2200 may include greater or fewer operations than those illustrated. Moreover, method 2200 may execute its operations in an order different than those illustrated below. Method 2200 may terminate at any suitable operation. Moreover, method 2200 may repeat operation at any suitable operation. Method 2200 may perform any of its operations in parallel with other operations of method 2200, or in parallel with operations of other methods.

Furthermore, method 2200 may be executed multiple times to determine when and whether to update the cache replacement policies applied to different groups of sets in a set associative cache or in multiple set associative caches. Method 2200 may be executed over time to update the cache replacement policies applied to a set associative cache, or to portions thereof, in response to changing workloads or other conditions. Based upon the results of method 2200, other methods may be invoked. In some embodiments, method 2200 may be invoked during the execution of method 1900 to perform some of the operations of method 1900.

At 2205, in one embodiment, a respective initial cache replacement policy is associated with each of two dedicated groups of sets of a set associative cache in a processor, and the remaining follower sets are associated with the more conservative one of the two cache replacement policies. In one example, the two cache replacement policies may include a less conservative cache replacement policy (such as a cache replacement policy in which cache lines are inserted in a manner that makes them immediately eligible for eviction from the cache) and a more conservative cache replacement policy (such as a cache replacement policy in which cache lines are inserted in a manner that delays their eligibility for eviction from the set associative cache), and the follower sets may initially be associated with the more conservative of the two cache replacement policies.

At 2210, during the current epoch, cache lines are inserted into the cache in accordance with the replacement policies associated with the sets corresponding to each of the cache lines. At 2215, at the end of the current epoch, the cache replacement policies for the two dedicated groups of sets are swapped.

At 2220, it may be determined whether the less conservative cache replacement policy outperformed the more conservative cache replacement policy during two consecutive epochs. If so, method 2200 proceeds to 2225. Otherwise, method 2200 returns to 2210, where a new epoch begins. In at least some embodiments, beginning a new epoch may include resetting a performance indicator to an initial, default, or neutral value. For example, in embodiments in which a saturation counter is used to track the performance of the two cache replacement policies, the saturation counter may be reset to its midpoint value at the beginning of each epoch. In some embodiments, if it is determined that the less conservative cache replacement policy outperformed the more conservative cache replacement policy during the most recent epoch but not during two consecutive epochs, an indicator may be set to a value reflecting that the less conservative cache replacement policy outperformed the more conservative cache replacement policy during the most recent epoch. If the less conservative cache replacement policy does not outperform the more conservative cache replacement policy during the next epoch, this indicator may be reset to a value reflecting that the more conservative cache replacement policy remains the preferred policy for the follower sets.

At 2225, in response to determining that the less conservative cache replacement policy outperformed the more conservative cache replacement policy during two consecutive epochs, the follower sets are associated with the less conservative replacement policy for the next epoch. At 2230, during the next epoch, cache lines are inserted into the cache in accordance with the updated replacement policies, after which the cache replacement policies for the two dedicated groups of sets are again swapped. At 2235, it may be determined whether the more conservative cache replacement policy outperformed the less conservative cache replacement policy during this epoch. If so, method 2200 may proceed to 2240. Otherwise, method 2200 may return to 2230 to begin a subsequent epoch without updating the cache replacement policy for the follower sets. At 2240, in response to determining that the more conservative cache replacement policy outperformed the less conservative cache replacement policy even once, the follower sets are associated with the more conservative replacement policy. As illustrated in FIG. 22, method 220 may then return to 2210 and repeat the operations shown as 2210-2240, as appropriate, one or more times during the execution of instructions by the processor.

FIGS. 23A and 23B further illustrate the use of conservative set dueling for cache replacement, according to embodiments of the present disclosure, more specifically, FIG. 23A, which is identical to FIG. 21B, illustrates the mappings of the cache sets within cache 2110 to cache replacement policies following updates made to the mappings at the end of a first epoch. FIG. 23B illustrates the mappings of the cache sets within cache 2110 to cache replacement policies following updates made to the mappings at the end of a second epoch.

In FIG. 23A, the two groups of sets labeled 2112 and 2118 are dedicated to the second cache replacement policy in which cache lines are inserted with an NRU value of 0, and the two groups of sets labeled as 2114 and 2116 are dedicated to the first cache replacement policy in which cache lines are inserted with an NRU value of 1. As in the example illustrated in FIGS. 21A and 21B, the cache replacement policies for these two dedicated groups of sets are swapped at the end of the epoch, resulting in the cache replacement policy mapping shown in FIG. 23B.

In FIG. 23B, the two groups of sets labeled 2112 and 2118 are once again dedicated to the first cache replacement policy in which cache lines are inserted with an NRU value of 1, and the two groups of sets labeled as 2114 and 2116 are dedicated to the second cache replacement policy in which cache lines are inserted with an NRU value of 0. In this example, the second cache replacement policy again resulted in better performance than the first cache replacement policy for the most recent epoch. Since second cache replacement policy, which is less conservative than the first cache replacement policy, outperformed the first cache replacement policy for two consecutive epochs, the follower sets, including the group of sets labeled as 2121, the follower sets will use the second cache replacement policy for at least the next epoch. This is illustrated in FIG. 23B by the sparsely dotted background pattern on the follower sets. In this example, as long as the second cache replacement policy continues to outperform the first cache replacement policy, the follower sets will use the second cache replacement policy during subsequent epochs. However, if the first cache replacement policy outperforms the second cache replacement policy during even a single epoch, the follower sets will revert to using the first cache replacement policy until and unless the second cache replacement policy outperforms the first cache replacement policy during two consecutive epochs.

While several examples included herein describe the application of cache replacement techniques that employ policy swapping and conservative set dueling in systems in which there are only two cache replacement policies being compared against each other, in other embodiments, these techniques may be applied in systems that support more than two cache replacement policies. For example, in some embodiments, a system, processor, or cache controller may support three or more cache replacement policies. In one such embodiment, a different pair of cache replacement policies may be associated with two dedicated groups of sets and pitted against each other through conservative set dueling during different epochs. In this example, the results of the set dueling performed during a given epoch may affect the cache replacement policy that is associated with the follower sets for the next epoch and/or the two cache replacement policies to be pitted against each other during the next epoch. For example, in response to determining that a first one of the cache replacement policies involved in set dueling was outperformed by the second one of the cache replacement policies, the second cache replacement policy may be associated with the follower sets for the next epoch. In addition, a third cache replacement policy may be associated with one of the dedicated groups of sets, and may be pitted against the first cache replacement policy during the next epoch. As in embodiments in which there are only two cache replacement policies, there may be more evidence required to change the cache replacement policy associated with the follower sets to a cache replacement policy that is less conservative than the current cache replacement policy than to change the cache replacement policy associated with the follower sets to a cache replacement policy that is more conservative than the current cache replacement policy.

In some embodiments in which more than two cache replacement policies are supported, three or more of the cache replacement policies may be pitted against each other using conservative set dueling during a single epoch. For example, at least one cache replacement policy other than the first cache replacement policy and the second cache replacement policy may be associated with a respective additional group of sets in the set associative cache, such that the first, second, third, and additional groups of sets are non-overlapping. In this example, the third group of sets may represent the follower sets, and the first, second, and additional groups of sets may represent dedicated groups of sets, each of which may be associated with a different cache replacement policy during any given epoch. In some embodiments, in order to support set dueling between more than two cache replacement policies at a time, the cache controller may include more than one counter. In one example, the cache controller may include a separate counter for each cache replacement policy that is involved in a set dueling exercise, and that counter may be incremented each time there is a cache miss for an access directed to a portion of the cache associated with that cache replacement policy. In this example, the values of all the counters may be compared against each other at the end of each epoch to inform decisions about the cache replacement policy to be associated with the follower sets. In some embodiments, there may be more cache replacement policies supported than the number of cache replacement policies that can be involved in conservative set dueling at one time. In some embodiments, at least some of the mappings between the dedicated groups of sets and the cache replacement policies that are supported may change between epochs based on the results of the multiple-way set dueling. Here again, there may be more evidence required to change the cache replacement policy associated with the follower sets to a cache replacement policy that is less conservative than the current cache replacement policy than to change the cache replacement policy associated with the follower sets to a cache replacement policy that is more conservative than the current cache replacement policy.

While several examples included herein describe the application of cache replacement techniques that employ policy swapping and conservative set dueling in systems in which the groups of sets that are involved in set dueling are fixed, in other embodiments, the groups of sets that are involved in set dueling, or the membership of those sets, may, from time to time, be modified. For example, the cache controller may include circuitry or logic to modify the membership in at least one of the dedicated groups of sets or in the follower sets between epochs, for any of a variety of reasons. In some embodiments, such membership changes may be performed based on the results of a set dueling exercise. For example, if, based on the results of set dueling performed during one or more epochs, it becomes clear that the behavior or performance of the cache when accesses are directed a particular one of the dedicated groups of sets is not representative of the behavior of the cache as a whole, either generally or for a given application, the cache controller may modify the membership of one or more of the groups of sets in an attempt to identify dedicated groups of sets that are more suitable for use in determining which cache replacement policy should be associated with the follower sets. In some embodiments, the cache controller may, for at least one of the groups of sets involved in set dueling, select different members for the group of sets at the end of each epoch so that, over time, the set dueling exercise is applied to a larger sample of the sets in the cache. This approach may, in aggregate, better inform the selection of a cache replacement policy to be applied to the majority of the sets in the cache.

In at least some embodiments of the present disclosure, the systems and cache replacement techniques described herein that employ policy swapping and conservative set dueling may avoid the thrashing that can be common when applying existing set dueling techniques. For example, using an existing set dueling approach, if a particular group of sets always inserts new cache blocks with an NRU value of 0, each newly inserted cache block is already marked to be the next cache block evicted. The effect of this is that the same way is constantly being thrashed in each such sampled set. This allows very little time for any reuse of the cache blocks, even if they would have be reused if given more time. In extreme cases, this can cause significant performance loss if the sampled sets contain highly reused data that is constantly evicted. On the other hand, in the systems described herein that perform policy swapping between epochs and conservative set dueling, a benefit of swapping the cache replacement policies between groups of sets may be that each set group is able to spend at least some time inserting cache lines with an NRU value of 1. This may allow the set group to fill up all of its ways with potentially useful data before switching to a cache replacement policy in which cache lines are inserted with an NRU value of 0, which may cause thrashing on only one way in the sampled set.

This cache replacement techniques described herein that employ policy swapping and conservative set dueling have been tested through simulations, and have been found to increase performance across at least some trace lists, while increasing power consumption to a lesser degree, thereby achieving greater performance and energy efficiency at the same time. More specifically, these cache replacement techniques have been shown to simultaneously improve performance by lowering the miss-rate of the cache, and to lower energy consumption by avoiding the need to re-fetch data from main memory after is has been prematurely evicted.

Embodiments of the mechanisms disclosed herein may be implemented in hardware, software, firmware, or a combination of such implementation approaches. Embodiments of the disclosure may be implemented as computer programs or program code executing on programmable systems comprising at least one processor, a storage system (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device.

Program code may be applied to input instructions to perform the functions described herein and generate output information. The output information may be applied to one or more output devices, in known fashion. For purposes of this application, a processing system may include any system that has a processor, such as, for example; a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor.

The program code may be implemented in a high level procedural or object oriented programming language to communicate with a processing system. The program code may also be implemented in assembly or machine language, if desired. In fact, the mechanisms described herein are not limited in scope to any particular programming language. In any case, the language may be a compiled or interpreted language.

One or more aspects of at least one embodiment may be implemented by representative instructions stored on a machine-readable medium which represents various logic within the processor, which when read by a machine causes the machine to fabricate logic to perform the techniques described herein. Such representations, known as “IP cores” may be stored on a tangible, machine-readable medium and supplied to various customers or manufacturing facilities to load into the fabrication machines that actually make the logic or processor.

Such machine-readable storage media may include, without limitation, non-transitory, tangible arrangements of articles manufactured or formed by a machine or device, including storage media such as hard disks, any other type of disk including floppy disks, optical disks, compact disk read-only memories (CD-ROMs), compact disk rewritables (CD-RWs), and magneto-optical disks, semiconductor devices such as read-only memories (ROMs), random access memories (RAMs) such as dynamic random access memories (DRAMs), static random access memories (SRAMs), erasable programmable read-only memories (EPROMs), flash memories, electrically erasable programmable read-only memories (EEPROMs), magnetic or optical cards, or any other type of media suitable for storing electronic instructions.

Accordingly, embodiments of the disclosure may also include non-transitory, tangible machine-readable media containing instructions or containing design data, such as Hardware Description Language (HDL), which defines structures, circuits, apparatuses, processors and/or system features described herein. Such embodiments may also be referred to as program products.

In some cases, an instruction converter may be used to convert an instruction from a source instruction set to a target instruction set. For example, the instruction converter may translate (e.g., using static binary translation, dynamic binary translation including dynamic compilation), morph, emulate, or otherwise convert an instruction to one or more other instructions to be processed by the core. The instruction converter may be implemented in software, hardware, firmware, or a combination thereof. The instruction converter may be on processor, off processor, or part-on and part-off processor.

Thus, techniques for performing one or more instructions according to at least one embodiment are disclosed. While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of and not restrictive on other embodiments, and that such embodiments not be limited to the specific constructions and arrangements shown and described, since various other modifications may occur to those ordinarily skilled in the art upon studying this disclosure. In an area of technology such as this, where growth is fast and further advancements are not easily foreseen, the disclosed embodiments may be readily modifiable in arrangement and detail as facilitated by enabling technological advancements without departing from the principles of the present disclosure or the scope of the accompanying claims.

Some embodiments of the present disclosure include a processor. In at least some of these embodiments, the processor may include a set associative cache to store data in a plurality of cache lines, the cache lines to be organized in groups of sets. The organization of the cache lines into groups of sets may be dependent on a respective index value associated with each of the cache lines, and a cache controller. The cache controller may include circuitry to associate a first cache replacement policy with a first group of sets in the set associative cache, associate a second cache replacement policy with a second group of sets in the set associative cache, associate the first cache replacement policy with a third group of sets in the set associative cache, the first, second and third groups of sets being non-overlapping, and insert, during execution of instructions by the processor, a first plurality of cache lines into the set associative cache. The first, second and third groups of sets may collectively include all of the sets of the set associative cache. The circuitry to insert the first plurality of cache lines may include circuitry to insert each cache line in the first group of sets in accordance with the first cache replacement policy, insert each cache line in the second group of sets in accordance with the second cache replacement policy, and insert each cache line in the third group of sets in accordance with the first cache replacement policy. The cache controller may further include circuitry to detect, during insertion of the first plurality of cache lines, a condition to indicate that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped, and in response to detection of the condition, to associate the first cache replacement policy with the second group of sets, and to associate the second cache replacement policy with the first group of sets. In combination with any of the disclosed embodiments, the cache controller may further include circuitry to insert, subsequent to the swap of the associations, a second plurality of cache lines into the set associative cache. The circuitry to insert the second plurality of cache lines may include circuitry to insert each cache line in the second group of sets in accordance with the first cache replacement policy, and insert each cache line in the first group of sets in accordance with the second cache replacement policy. In combination with any of the above embodiments, the cache controller may further include circuitry to determine, prior to insertion of the second plurality of cache lines, that the first cache replacement policy resulted in better performance than the second cache replacement policy during insertion of the first plurality of cache lines, and to maintain, responsive to the determination that the first cache replacement policy resulted in better performance than the second cache replacement policy during insertion of the first plurality of cache lines, the association of the first cache replacement policy with the third group of sets. The circuitry to insert the second plurality of cache lines into the set associative cache may further include circuitry to insert each cache line in the third group of sets in accordance with the first cache replacement policy. In combination with any of the above embodiments, the cache controller may further include circuitry to determine, prior to insertion of the second plurality of cache lines, that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the first plurality of cache lines, and to associate, responsive to the determination that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the first plurality of cache lines, the second cache replacement policy with the third group of sets. The circuitry to insert the second plurality of cache lines into the set associative cache may further include circuitry to insert each cache line in the second group of sets in accordance with the second cache replacement policy. In combination with any of the above embodiments, the cache controller may further include circuitry to determine, prior to insertion of the first plurality of cache lines, that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of a third plurality of cache lines, to determine, prior to insertion of the second plurality of cache lines, that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the first plurality of cache lines, and to associate, responsive to the determination that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the third plurality of cache lines and during insertion of the first plurality of cache lines, the second cache replacement policy with the third group of sets. The circuitry to insert the second plurality of cache lines into the set associative cache may further include circuitry to insert each cache line in the second group of sets in accordance with the second cache replacement policy. In combination with any of the above embodiments, the cache controller may further include a counter, and circuitry to increment the counter responsive to a cache miss for a cache line in the second group of sets, and to decrement the counter responsive to a cache miss for a cache line in the first group of sets. The circuitry to detect a condition to indicate that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped may include circuitry to determine that the value of the counter meets a predetermined threshold value to indicate that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped. In any of the above embodiments, the predetermined threshold value may represent a high or low saturation value for the counter. In any of the above embodiments, the predetermined threshold value may represent a predetermined percentage of a saturation value for the counter. In combination with any of the above embodiments, the cache controller may further include circuitry to reset the counter to an initial value, a default value, or a midpoint value between insertion of the first plurality of cache lines and insertion of the second plurality of cache lines. In combination with any of the above embodiments, the circuitry to detect a condition to indicate that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped may include circuitry to determine that a predetermined amount of time has passed since the current associations between the first and second groups of sets and the first and second cache replacement policies were made. In combination with any of the above embodiments, the circuitry to associate the first cache replacement policy with a first group of sets in the set associative cache may include circuitry to randomly select one or more sets for inclusion in the first group of sets from among all sets in the set associative cache, and the circuitry to associate the second cache replacement policy with a second group of sets in the set associative cache may include circuitry to randomly select one or more sets for inclusion in the second group of sets from among sets not included in the first group of sets. In combination with any of the above embodiments, the first cache replacement policy may specify that each cache line is to be inserted in a manner that delays its eviction from the set associative cache, and the second cache replacement policy may specify that each cache line is to be inserted in a manner that makes it eligible for eviction from the set associative cache. In any of the above embodiments, the first cache replacement policy may specify that each cache line is to be inserted in a manner that makes it eligible for eviction from the set associative cache, and the second cache replacement policy may specify that each cache line is to be inserted in a manner that delays its eviction from the set associative cache. In any of the above embodiments, the first and second cache replacement policies may specify different cache line eviction policies. In any of the above embodiments, the first cache replacement policy may be one of a plurality of cache replacement policies supported in the cache controller, and the plurality of cache replacement policies may include three or more cache replacement policies. In combination with any of the above embodiments, the cache controller may further include circuitry to associate at least one cache replacement policy of the plurality of cache replacement policies other than the first cache replacement policy and the second cache replacement policy with a respective additional group of sets in the set associative cache, the first, second, third, and additional groups of sets being non-overlapping. The circuitry to insert the first plurality of cache lines into the set associative cache further includes circuitry to insert each cache line in each additional group of sets in accordance with the cache replacement policy currently associated with the additional group of sets. The circuitry to detect a condition to indicate that at least one of the association between the first cache replacement policy and the first group of sets and the association between the second cache replacement policy and the second group of sets is to be modified may further include circuitry to determine whether the respective cache replacement policy associated with one of the additional groups of sets in the set associative cache is to be modified. The cache controller may further include circuitry to associate, responsive to a determination that the respective cache replacement policy associated with one of the additional groups of sets in the set associative cache is to be modified, a third alternate cache replacement policy with the one of the additional groups of sets, the third alternate cache replacement policy being one of the plurality of cache replacement policies other than the cache replacement policy previously associated with the one of the additional groups of sets. In combination with any of the above embodiments, the cache controller may further include circuitry to modify, prior to insertion of the second plurality of cache lines, membership in at least one of the first, second, and third groups of sets.

Some embodiments of the present disclosure include a method for executing instructions. In at least some of these embodiments, the method may include, in a processor, associating a first cache replacement policy with a first group of sets in a set associative cache, the set associative cache storing data in a plurality of cache lines organized in groups of sets, associating a second cache replacement policy with a second group of sets in the set associative cache, and associating the first cache replacement policy with a third group of sets in the set associative cache, the first, second and third groups of sets being non-overlapping. The organization of the cache lines into groups of sets may be dependent on a respective index value associated with each of the cache lines. The first, second and third groups of sets may collectively include all of the sets of the set associative cache. The method may also include inserting, during execution of instructions by the processor, a first plurality of cache lines into the set associative cache, including inserting each cache line in the first group of sets in accordance with the first cache replacement policy, inserting each cache line in the second group of sets in accordance with the second cache replacement policy, and inserting each cache line in the third group of sets in accordance with the first cache replacement policy. The method may also include detecting, while inserting the first plurality of cache lines, a condition indicating that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped, and in response to detecting the condition, associating the first cache replacement policy with the second group of sets, and associating the second cache replacement policy with the first group of sets. In combination with any of the disclosed embodiments, the method may include inserting, subsequent to swapping the associations, a second plurality of cache lines into the set associative cache, including inserting each cache line in the second group of sets in accordance with the first cache replacement policy, and inserting each cache line in the first group of sets in accordance with the second cache replacement policy. In combination with any of the above embodiments, the method may further include determining, prior to inserting the second plurality of cache lines, that the first cache replacement policy resulted in better performance than the second cache replacement policy during insertion of the first plurality of cache lines, and maintaining, in response to determining that the first cache replacement policy resulted in better performance than the second cache replacement policy during insertion of the first plurality of cache lines, the association of the first cache replacement policy with the third group of sets. Inserting the second plurality of cache lines into the set associative cache may further include inserting each cache line in the third group of sets in accordance with the first cache replacement policy. In combination with any of the above embodiments, the method may further include determining, prior to inserting the second plurality of cache lines, that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the first plurality of cache lines, and associating, in response to determining that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the first plurality of cache lines, the second cache replacement policy with the third group of sets. Inserting the second plurality of cache lines into the set associative cache may further include inserting each cache line in the second group of sets in accordance with the second cache replacement policy. In combination with any of the above embodiments, the method may further include determining, prior to inserting the first plurality of cache lines, that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of a third plurality of cache lines, determining, prior to inserting the second plurality of cache lines, that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the first plurality of cache lines, and associating, in response to determining that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the third plurality of cache lines and during insertion of the first plurality of cache lines, the second cache replacement policy with the third group of sets. Inserting the second plurality of cache lines into the set associative cache may further include inserting each cache line in the second group of sets in accordance with the second cache replacement policy. In combination with any of the above embodiments, the method may further include incrementing a counter in response to a cache miss for a cache line in the second group of sets, and decrementing the counter in response to a cache miss for a cache line in the first group of sets. Detecting a condition indicating that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped may include determining that the value of the counter meets a predetermined threshold value indicating that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped. In any of the above embodiments, the predetermined threshold value may represent a high or low saturation value for the counter. In any of the above embodiments, the predetermined threshold value may represent a predetermined percentage of a saturation value for the counter. In combination with any of the above embodiments, the method may further include resetting the counter to an initial value, a default value, or a midpoint value between the inserting of the first plurality of cache lines and the inserting of the second plurality of cache lines. In any of the above embodiments, detecting a condition indicating that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped may include determining that a predetermined amount of time has passed since the current associations between the first and second groups of sets and the first and second cache replacement policies were made. In any of the above embodiments, associating the first cache replacement policy with a first group of sets in the set associative cache may include randomly selecting one or more sets for inclusion in the first group of sets from among all sets in the set associative cache, and associating the second cache replacement policy with a second group of sets in the set associative cache may include randomly selecting one or more sets for inclusion in the second group of sets from among sets not included in the first group of sets. In any of the above embodiments, the first cache replacement policy may specify that each cache line is to be inserted in a manner that delays its eviction from the set associative cache, and the second cache replacement policy may specify that each cache line is to be inserted in a manner that makes it eligible for eviction from the set associative cache. In any of the above embodiments, the first cache replacement policy may specify that each cache line is to be inserted in a manner that makes it eligible for eviction from the set associative cache, and the second cache replacement policy may specify that each cache line is to be inserted in a manner that delays its eviction from the set associative cache. In any of the above embodiments, the first and second cache replacement policies may specify different cache line eviction policies. In any of the above embodiments, the first cache replacement policy may be one of a plurality of cache replacement policies supported in the processor, and the plurality of cache replacement policies may include three or more cache replacement policies. In combination with any of the above embodiments, the method may include associating at least one cache replacement policy of the plurality of cache replacement policies other than the first cache replacement policy and the second cache replacement policy with a respective additional group of sets in the set associative cache, the first, second, third, and additional groups of sets being non-overlapping. Inserting the first plurality of cache lines into the set associative cache may include inserting each cache line in each additional group of sets in accordance with the cache replacement policy currently associated with the additional group of sets. Detecting a condition to indicate that at least one of the association between the first cache replacement policy and the first group of sets and the association between the second cache replacement policy and the second group of sets is to be modified may further include determining whether the respective cache replacement policy associated with one of the additional groups of sets in the set associative cache is to be modified. The method may further include associating, in response to a determination that the respective cache replacement policy associated with one of the additional groups of sets in the set associative cache is to be modified, a third alternate cache replacement policy with the one of the additional groups of sets, the third alternate cache replacement policy being one of the plurality of cache replacement policies other than the cache replacement policy previously associated with the one of the additional groups of sets. In combination with any of the above embodiments, the method may further include modifying, prior to insertion of the second plurality of cache lines, membership in at least one of the first, second, and third groups of sets.

Some embodiments of the present disclosure include a cache controller. In at least some of these embodiments, the cache controller may include circuitry to associate a first cache replacement policy with a first group of sets in a set associative cache, the set associative cache storing data in a plurality of cache lines organized in groups of sets, and the first cache replacement policy being one of a plurality of cache replacement policies supported in the cache controller, and to associate a second cache replacement policy of the plurality of cache replacement policies with a second group of sets in the set associative cache; associate the first cache replacement policy with a third group of sets in the set associative cache, the first, second and third groups of sets being non-overlapping. The organization of the cache lines into groups of sets may be dependent on a respective index value associated with each of the cache lines. The cache controller may also include circuitry to insert a first plurality of cache lines into the set associative cache, including circuitry to insert each cache line in the first group of sets in accordance with the first cache replacement policy, to insert each cache line in the second group of sets in accordance with the second cache replacement policy, and to insert each cache line in the third group of sets in accordance with the first cache replacement policy. The cache controller may also include circuitry to detect, during insertion of the first plurality of cache lines, a condition to indicate that at least one of the association between the first cache replacement policy and the first group of sets and the association between the second cache replacement policy and the second group of sets is to be modified, and circuitry to associate, in response to detection of the condition, a first alternate cache replacement policy with the first group of sets, the first alternate cache replacement policy being one of the plurality of cache replacement policies other than the first cache replacement policy, or to associate a second alternate cache replacement policy with the second group of sets, the second alternate cache replacement policy being one of the plurality of cache replacement policies other than the second cache replacement policy. In any of the disclosed embodiments, the cache controller may also include circuitry to insert, subsequent to the modification of at least one of the associations, a second plurality of cache lines into the set associative cache, including circuitry to insert each cache line in the first group of sets in accordance with the cache replacement policy currently associated with the first group of sets, and to insert each cache line in the second group of sets in accordance with the cache replacement policy currently associated with the second group of sets. In combination with any of the above embodiments, the cache controller may further include circuitry to determine, prior to insertion of the second plurality of cache lines, that the first cache replacement policy resulted in better performance than the second cache replacement policy during insertion of the first plurality of cache lines, and to maintain, responsive to the determination that the first cache replacement policy resulted in better performance than the second cache replacement policy during insertion of the first plurality of cache lines, the association of the first cache replacement policy with the third group of sets. The circuitry to insert the second plurality of cache lines into the set associative cache may further include circuitry to insert each cache line in the third group of sets in accordance with the first cache replacement policy. In combination with any of the above embodiments, the cache controller may further include circuitry to determine, prior to insertion of the second plurality of cache lines, that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the first plurality of cache lines, and to associate, responsive to the determination that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the first plurality of cache lines, the second cache replacement policy with the third group of sets. The circuitry to insert the second plurality of cache lines into the set associative cache may further include circuitry to insert each cache line in the second group of sets in accordance with the second cache replacement policy. In combination with any of the above embodiments, the cache controller may further include circuitry to determine, prior to insertion of the first plurality of cache lines, that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of a third plurality of cache lines, to determine, prior to insertion of the second plurality of cache lines, that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the first plurality of cache lines, and to associate, responsive to the determination that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the third plurality of cache lines and during insertion of the first plurality of cache lines, the second cache replacement policy with the third group of sets. The circuitry to insert the second plurality of cache lines into the set associative cache may further include circuitry to insert each cache line in the second group of sets in accordance with the second cache replacement policy. In combination with any of the above embodiments, the cache controller may further include a counter, and circuitry to increment the counter responsive to a cache miss for a cache line in the second group of sets, and to decrement the counter responsive to a cache miss for a cache line in the first group of sets. The circuitry to detect a condition to indicate that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped may include circuitry to determine that the value of the counter meets a predetermined threshold value to indicate that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped. In any of the above embodiments, the predetermined threshold value may represent a high or low saturation value for the counter. In any of the above embodiments, the predetermined threshold value may represent a predetermined percentage of a saturation value for the counter. In combination with any of the above embodiments, the cache controller may further include circuitry to reset the counter to an initial value, a default value, or a midpoint value between insertion of the first plurality of cache lines and insertion of the second plurality of cache lines. In combination with any of the above embodiments, the circuitry to detect a condition to indicate that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped may include circuitry to determine that a predetermined amount of time has passed since the current associations between the first and second groups of sets and the first and second cache replacement policies were made. In combination with any of the above embodiments, the circuitry to associate the first cache replacement policy with a first group of sets in the set associative cache may include circuitry to randomly select one or more sets for inclusion in the first group of sets from among all sets in the set associative cache, and the circuitry to associate the second cache replacement policy with a second group of sets in the set associative cache may include circuitry to randomly select one or more sets for inclusion in the second group of sets from among sets not included in the first group of sets. In combination with any of the above embodiments, the first cache replacement policy may specify that each cache line is to be inserted in a manner that delays its eviction from the set associative cache, and the second cache replacement policy may specify that each cache line is to be inserted in a manner that makes it eligible for eviction from the set associative cache. In any of the above embodiments, the first cache replacement policy may specify that each cache line is to be inserted in a manner that makes it eligible for eviction from the set associative cache, and the second cache replacement policy may specify that each cache line is to be inserted in a manner that delays its eviction from the set associative cache. In any of the above embodiments, the first and second cache replacement policies may specify different cache line eviction policies. In any of the above embodiments, the first cache replacement policy may be one of a plurality of cache replacement policies supported in the cache controller, and the plurality of cache replacement policies may include three or more cache replacement policies. In combination with any of the above embodiments, the cache controller may further include circuitry to associate at least one cache replacement policy of the plurality of cache replacement policies other than the first cache replacement policy and the second cache replacement policy with a respective additional group of sets in the set associative cache, the first, second, third, and additional groups of sets being non-overlapping. The circuitry to insert the first plurality of cache lines into the set associative cache further includes circuitry to insert each cache line in each additional group of sets in accordance with the cache replacement policy currently associated with the additional group of sets. The circuitry to detect a condition to indicate that at least one of the association between the first cache replacement policy and the first group of sets and the association between the second cache replacement policy and the second group of sets is to be modified may further include circuitry to determine whether the respective cache replacement policy associated with one of the additional groups of sets in the set associative cache is to be modified. The cache controller may further include circuitry to associate, responsive to a determination that the respective cache replacement policy associated with one of the additional groups of sets in the set associative cache is to be modified, a third alternate cache replacement policy with the one of the additional groups of sets, the third alternate cache replacement policy being one of the plurality of cache replacement policies other than the cache replacement policy previously associated with the one of the additional groups of sets. In combination with any of the above embodiments, the cache controller may further include circuitry to modify, prior to insertion of the second plurality of cache lines, membership in at least one of the first, second, and third groups of sets.

Some embodiments of the present disclosure include a system for executing instructions. In at least some of these embodiments, the system may include means for associating a first cache replacement policy with a first group of sets in a set associative cache, the set associative cache storing data in a plurality of cache lines organized in groups of sets, means for associating a second cache replacement policy with a second group of sets in the set associative cache, and means for associating the first cache replacement policy with a third group of sets in the set associative cache, the first, second and third groups of sets being non-overlapping. The organization of the cache lines into groups of sets may be dependent on a respective index value associated with each of the cache lines. The first, second and third groups of sets may collectively include all of the sets of the set associative cache. The system may also include means for inserting, during execution of instructions by the processor, a first plurality of cache lines into the set associative cache, including means for inserting each cache line in the first group of sets in accordance with the first cache replacement policy, means for inserting each cache line in the second group of sets in accordance with the second cache replacement policy, and means for inserting each cache line in the third group of sets in accordance with the first cache replacement policy. The system may also include means for detecting, while inserting the first plurality of cache lines, a condition indicating that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped and means for associating, responsive to detection of the condition, the first cache replacement policy with the second group of sets and the second cache replacement policy with the first group of sets. In combination with any of the disclosed embodiments, the apparatus may further include means for inserting, subsequent to swapping the associations, a second plurality of cache lines into the set associative cache, including means for inserting each cache line in the second group of sets in accordance with the first cache replacement policy, and means for inserting each cache line in the first group of sets in accordance with the second cache replacement policy. In combination with any of the above embodiments, the system may further include means for determining, prior to inserting the second plurality of cache lines, that the first cache replacement policy resulted in better performance than the second cache replacement policy during insertion of the first plurality of cache lines, and means for maintaining, in response to determining that the first cache replacement policy resulted in better performance than the second cache replacement policy during insertion of the first plurality of cache lines, the association of the first cache replacement policy with the third group of sets. The means for inserting the second plurality of cache lines into the set associative cache may further include means for inserting each cache line in the third group of sets in accordance with the first cache replacement policy. In combination with any of the above embodiments, the system may further include means for determining, prior to inserting the second plurality of cache lines, that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the first plurality of cache lines, and means for associating, in response to determining that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the first plurality of cache lines, the second cache replacement policy with the third group of sets. The means for inserting the second plurality of cache lines into the set associative cache may further include means for inserting each cache line in the second group of sets in accordance with the second cache replacement policy. In combination with any of the above embodiments, the system may further include means for determining, prior to inserting the first plurality of cache lines, that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of a third plurality of cache lines, means for determining, prior to inserting the second plurality of cache lines, that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the first plurality of cache lines, and means for associating, in response to determining that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the third plurality of cache lines and during insertion of the first plurality of cache lines, the second cache replacement policy with the third group of sets. The means for inserting the second plurality of cache lines into the set associative cache may further include means for inserting each cache line in the second group of sets in accordance with the second cache replacement policy. In combination with any of the above embodiments, the system may further include means for incrementing a counter in response to a cache miss for a cache line in the second group of sets, and means for decrementing the counter in response to a cache miss for a cache line in the first group of sets. The means for detecting a condition indicating that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped may include means for determining that the value of the counter meets a predetermined threshold value indicating that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped. In any of the above embodiments, the predetermined threshold value may represent a high or low saturation value for the counter. In any of the above embodiments, the predetermined threshold value may represent a predetermined percentage of a saturation value for the counter. In combination with any of the above embodiments, the system may further include means for resetting the counter to an initial value, a default value, or a midpoint value between the inserting of the first plurality of cache lines and the inserting of the second plurality of cache lines. In any of the above embodiments, the means for detecting a condition indicating that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped may include means for determining that a predetermined amount of time has passed since the current associations between the first and second groups of sets and the first and second cache replacement policies were made. In any of the above embodiments, the means for associating the first cache replacement policy with a first group of sets in the set associative cache may include means for randomly selecting one or more sets for inclusion in the first group of sets from among all sets in the set associative cache, and the means for associating the second cache replacement policy with a second group of sets in the set associative cache may include means for randomly selecting one or more sets for inclusion in the second group of sets from among sets not included in the first group of sets. In any of the above embodiments, the first cache replacement policy may specify that each cache line is to be inserted in a manner that delays its eviction from the set associative cache, and the second cache replacement policy may specify that each cache line is to be inserted in a manner that makes it eligible for eviction from the set associative cache. In any of the above embodiments, the first cache replacement policy may specify that each cache line is to be inserted in a manner that makes it eligible for eviction from the set associative cache, and the second cache replacement policy may specify that each cache line is to be inserted in a manner that delays its eviction from the set associative cache. In any of the above embodiments, the first and second cache replacement policies may specify different cache line eviction policies. In any of the above embodiments, the first cache replacement policy may be one of a plurality of cache replacement policies supported in the system, and the plurality of cache replacement policies may include three or more cache replacement policies. In combination with any of the above embodiments, the system may include means for associating at least one cache replacement policy of the plurality of cache replacement policies other than the first cache replacement policy and the second cache replacement policy with a respective additional group of sets in the set associative cache, the first, second, third, and additional groups of sets being non-overlapping. The means for inserting the first plurality of cache lines into the set associative cache may include means for inserting each cache line in each additional group of sets in accordance with the cache replacement policy currently associated with the additional group of sets. The means for detecting a condition to indicate that at least one of the association between the first cache replacement policy and the first group of sets and the association between the second cache replacement policy and the second group of sets is to be modified may further include means for determining whether the respective cache replacement policy associated with one of the additional groups of sets in the set associative cache is to be modified. The system may further include means for associating, in response to a determination that the respective cache replacement policy associated with one of the additional groups of sets in the set associative cache is to be modified, a third alternate cache replacement policy with the one of the additional groups of sets, the third alternate cache replacement policy being one of the plurality of cache replacement policies other than the cache replacement policy previously associated with the one of the additional groups of sets. In combination with any of the above embodiments, the system may further include means for modifying, prior to insertion of the second plurality of cache lines, membership in at least one of the first, second, and third groups of sets. 

1. A processor, comprising: a set associative cache to store data in a plurality of cache lines, the cache lines being organized in groups of sets; a cache controller including circuitry to: associate a first cache replacement policy with a first group of sets; associate a second cache replacement policy with a second group of sets; associate the first cache replacement policy with a third group of sets, the first, second and third groups of sets in the set associative cache being non-overlapping; insert, during execution of instructions by the processor, a first plurality of cache lines into the set associative cache, including circuitry to: insert each cache line in the first group of sets and in the third group of sets in accordance with the first cache replacement policy; insert each cache line in the second group of sets in accordance with the second cache replacement policy; detect a condition to indicate that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped; in response to detection of the condition: associate the first cache replacement policy with the second group of sets; associate the second cache replacement policy with the first group of sets.
 2. The processor of claim 1, wherein: the cache controller further includes circuitry to: determine that the first cache replacement policy resulted in better performance than the second cache replacement policy during insertion of the first plurality of cache lines; maintain, responsive to the determination that the first cache replacement policy resulted in better performance than the second cache replacement policy during insertion of the first plurality of cache lines, the association of the first cache replacement policy with the third group of sets; insert a second plurality of cache lines into the set associative cache, including circuitry to: insert each cache line in the second group of sets in accordance with the first cache replacement policy; insert each cache line in the first group of sets in accordance with the second cache replacement policy; insert each cache line in the third group of sets in accordance with the first cache replacement policy.
 3. The processor of claim 1, wherein: the cache controller further includes circuitry to: determine that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the first plurality of cache lines; associate, responsive to the determination that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the first plurality of cache lines, the second cache replacement policy with the third group of sets; insert a second plurality of cache lines into the set associative cache, including circuitry to: insert each cache line in the second group of sets in accordance with the first cache replacement policy; insert each cache line in the first group of sets in accordance with the second cache replacement policy; insert each cache line in the third group of sets in accordance with the second cache replacement policy.
 4. The processor of claim 1, wherein: the cache controller further includes circuitry to: determine, prior to insertion of the first plurality of cache lines, that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of a third plurality of cache lines; determine that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the first plurality of cache lines; associate, responsive to the determination that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the third plurality of cache lines and during insertion of the first plurality of cache lines, the second cache replacement policy with the third group of sets; insert a second plurality of cache lines into the set associative cache, including circuitry to: insert each cache line in the second group of sets in accordance with the first cache replacement policy; insert each cache line in the first group of sets in accordance with the second cache replacement policy; insert each cache line in the third group of sets in accordance with the second cache replacement policy.
 5. The processor of claim 1, wherein: the cache controller further includes: a counter; circuitry to: increment the counter responsive to a cache miss for a cache line in the second group of sets; decrement the counter responsive to a cache miss for a cache line in the first group of sets; the circuitry to detect a condition to indicate that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped includes circuitry to: determine that the value of the counter meets a predetermined threshold value to indicate that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped.
 6. The processor of claim 1, wherein: the circuitry to detect a condition to indicate that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped includes circuitry to: determine that a predetermined amount of time has passed since the current associations between the first and second groups of sets and the first and second cache replacement policies were made.
 7. The processor of claim 1, wherein: the circuitry to associate the first cache replacement policy with a first group of sets in the set associative cache includes circuitry to: randomly select one or more sets for inclusion in the first group of sets from among all sets in the set associative cache; the circuitry to associate the second cache replacement policy with a second group of sets in the set associative cache includes circuitry to: randomly select one or more sets for inclusion in the second group of sets from among sets not included in the first group of sets.
 8. The processor of claim 1, wherein: the first cache replacement policy specifies that each cache line is to be inserted in a manner that delays its eviction from the set associative cache; the second cache replacement policy specifies that each cache line is to be inserted in a manner that makes it eligible for eviction from the set associative cache.
 9. A method, comprising, in a processor: associating a first cache replacement policy with a first group of sets in a set associative cache, the set associative cache storing data in a plurality of cache lines in groups of sets; associating a second cache replacement policy with a second group of sets; associating the first cache replacement policy with a third group of sets; inserting, during execution of instructions by the processor, a first plurality of cache lines into the set associative cache, including: inserting each cache line in the first group of sets and in the third group of sets in accordance with the first cache replacement policy; inserting each cache line in the second group of sets in accordance with the second cache replacement policy; detecting a condition indicating that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped; associating the first cache replacement policy with the second group of sets; associating the second cache replacement policy with the first group of sets.
 10. The method of claim 9, wherein the method further includes: determining that the first cache replacement policy resulted in better performance than the second cache replacement policy during insertion of the first plurality of cache lines; maintaining, in response to determining that the first cache replacement policy resulted in better performance than the second cache replacement policy during insertion of the first plurality of cache lines, the association of the first cache replacement policy with the third group of sets; inserting a second plurality of cache lines into the set associative cache including: inserting each cache line in the second group of sets in accordance with the first cache replacement policy; inserting each cache line in the first group of sets in accordance with the second cache replacement policy; inserting each cache line in the third group of sets in accordance with the first cache replacement policy.
 11. The method of claim 9, wherein the method further includes: determining that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the first plurality of cache lines; associating, in response to determining that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the first plurality of cache lines, the second cache replacement policy with the third group of sets; inserting a second plurality of cache lines into the set associative cache including: inserting each cache line in the second group of sets in accordance with the first cache replacement policy; inserting each cache line in the first group of sets in accordance with the second cache replacement policy; inserting each cache line in the third group of sets in accordance with the second cache replacement policy.
 12. The method of claim 9, wherein the method further includes: determining, prior to inserting the first plurality of cache lines, that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of a third plurality of cache lines; determining that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the first plurality of cache lines; associating, in response to determining that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the third plurality of cache lines and during insertion of the first plurality of cache lines, the second cache replacement policy with the third group of sets; inserting a second plurality of cache lines into the set associative cache including: inserting each cache line in the second group of sets in accordance with the first cache replacement policy; inserting each cache line in the first group of sets in accordance with the second cache replacement policy; inserting each cache line in the third group of sets in accordance with the second cache replacement policy.
 13. The method of claim 9, wherein: the method further includes: incrementing a counter in response to a cache miss for a cache line in the second group of sets; decrementing the counter in response to a cache miss for a cache line in the first group of sets; detecting a condition indicating that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped includes: determining that the value of the counter meets a predetermined threshold value indicating that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped.
 14. The method of claim 9, wherein: detecting a condition indicating that the associations between the first and second groups of sets and the first and second cache replacement policies are to be swapped includes: determining that a predetermined amount of time has passed since the current associations between the first and second groups of sets and the first and second cache replacement policies were made.
 15. The method of claim 9, wherein: associating the first cache replacement policy with a first group of sets in the set associative cache includes: randomly selecting one or more sets for inclusion in the first group of sets from among all sets in the set associative cache; associating the second cache replacement policy with a second group of sets in the set associative cache includes: randomly selecting one or more sets for inclusion in the second group of sets from among sets not included in the first group of sets.
 16. A cache controller, comprising circuitry to: associate a first one of a plurality of supported cache replacement policies with a first group of sets in a set associative cache, the set associative cache storing data in a plurality of cache lines organized in groups of sets; associate a second one of the cache replacement policies with a second group of sets; associate the first cache replacement policy with a third group of sets, the first, second and third groups of sets in the set associative cache being non-overlapping; insert a first plurality of cache lines into the set associative cache, including circuitry to: insert each cache line in the first group of sets and in the third group of sets in accordance with the first cache replacement policy; insert each cache line in the second group of sets in accordance with the second cache replacement policy; detect a condition to indicate that at least one of the association between the first cache replacement policy and the first group of sets and the association between the second cache replacement policy and the second group of sets is to be modified; in response to detection of the condition: associate a first alternate cache replacement policy with the first group of sets, the first alternate cache replacement policy being one of the plurality of supported cache replacement policies other than the first cache replacement policy; or associate a second alternate cache replacement policy with the second group of sets, the second alternate cache replacement policy being one of the plurality of supported cache replacement policies other than the second cache replacement policy.
 17. The cache controller of claim 16, wherein the cache controller further includes circuitry to: determine whether the first cache replacement policy or the second cache replacement policy resulted in better performance during insertion of the first plurality of cache lines; maintain, responsive to a determination that the first cache replacement policy resulted in better performance than the second cache replacement policy during insertion of the first plurality of cache lines, the association of the first cache replacement policy with the third group of sets; associate, responsive to a determination that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the first plurality of cache lines, the second cache replacement policy with the third group of sets; insert, subsequent to the modification of at least one of the associations, a second plurality of cache lines into the set associative cache, including circuitry to: insert each cache line in the first group of sets in accordance with the cache replacement policy currently associated with the first group of sets; insert each cache line in the second group of sets in accordance with the cache replacement policy currently associated with the second group of sets; insert each cache line in the third group of sets in accordance with the currently associated cache replacement policy.
 18. The cache controller of claim 16, wherein the cache controller further includes circuitry to: determine, prior to insertion of the first plurality of cache lines, that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of a third plurality of cache lines; determine that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the first plurality of cache lines; associate, responsive to the determination that the second cache replacement policy resulted in better performance than the first cache replacement policy during insertion of the third plurality of cache lines and during insertion of the first plurality of cache lines, the second cache replacement policy with the third group of sets; insert, subsequent to the modification of at least one of the associations, a second plurality of cache lines into the set associative cache, including circuitry to: insert each cache line in the first group of sets in accordance with the cache replacement policy currently associated with the first group of sets; insert each cache line in the second group of sets in accordance with the cache replacement policy currently associated with the second group of sets; insert each cache line in the second group of sets in accordance with the second cache replacement policy.
 19. The cache controller of claim 16, wherein: the cache controller further includes circuitry to: associate at least one cache replacement policy of the plurality of cache replacement policies other than the first cache replacement policy and the second cache replacement policy with a respective additional group of sets in the set associative cache, the first, second, third, and additional groups of sets being non-overlapping; the circuitry to insert the first plurality of cache lines into the set associative cache further includes circuitry to: insert each cache line in each additional group of sets in accordance with the cache replacement policy currently associated with the additional group of sets; the circuitry to detect a condition to indicate that at least one of the association between the first cache replacement policy and the first group of sets and the association between the second cache replacement policy and the second group of sets is to be modified further includes circuitry to: determine whether the respective cache replacement policy associated with one of the additional groups of sets in the set associative cache is to be modified; the cache controller further includes circuitry to: associate, responsive to a determination that the respective cache replacement policy associated with one of the additional groups of sets in the set associative cache is to be modified, a third alternate cache replacement policy with the one of the additional groups of sets, the third alternate cache replacement policy being one of the plurality of supported cache replacement policies other than the cache replacement policy previously associated with the one of the additional groups of sets.
 20. The cache controller of claim 16, wherein the cache controller further includes circuitry to: modify, prior to insertion of the second plurality of cache lines, membership in at least one of the first, second, and third groups of sets. 